Triple
T28712084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Mulk |
E729855
|
entity |
| Predicate | positionInTitle |
P21675
|
FINISHED |
| Object | usually final element |
—
|
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: usually final element | Statement: [al-Mulk, positionInTitle, usually final element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTitle Context triple: [al-Mulk, positionInTitle, usually final element]
-
A.
titlePositionRelation
chosen
Indicates a relationship specifying how a title is positioned or ordered relative to other titles or elements.
-
B.
associatedTitleLocation
Indicates a relationship where a title is linked to a specific location with which it is contextually or formally connected.
-
C.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
D.
namePosition
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
E.
positionTerm
Indicates that one entity holds, is assigned, or is described by a specific role, title, or positional designation in relation to another entity.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 28, 2026, 5:48 a.m.