Triple
T31524718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Ireland |
E804303
|
entity |
| Predicate | hasComparativeRole |
P41879
|
FINISHED |
| Object | similar to role of Prince of Wales in Wales |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: similar to role of Prince of Wales in Wales | Statement: [Prince of Ireland, hasComparativeRole, similar to role of Prince of Wales in Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComparativeRole Context triple: [Prince of Ireland, hasComparativeRole, similar to role of Prince of Wales in Wales]
-
A.
comparativeRole
chosen
Indicates a relationship where one entity’s role is compared to another’s in terms of level, importance, or function.
-
B.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
C.
hasCompanionRoleIn
Indicates that an entity serves in a companion or supporting role within a specified context, activity, or relationship.
-
D.
hasCompanionRoleTo
Indicates that one entity serves in a companion or supporting role in relation to another entity.
-
E.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
Created at: April 30, 2026, 9:58 p.m.