Triple
T1353147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qasim ibn Muhammad |
E28927
|
entity |
| Predicate | positionInSiblings |
P20593
|
FINISHED |
| Object | eldest son of Muhammad |
—
|
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: eldest son of Muhammad | Statement: [Qasim ibn Muhammad, positionInSiblings, eldest son of Muhammad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSiblings Context triple: [Qasim ibn Muhammad, positionInSiblings, eldest son of Muhammad]
-
A.
positionInHierarchy
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
B.
positionInFamilyBirthOrder
chosen
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
C.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
D.
siblingCount
Indicates the number of siblings an entity has.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26d0c4481908fddda89242a57b3 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.