Triple
T34115364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferdinand of Castile, Lord of Ledesma |
E874955
|
entity |
| Predicate | relativePositionInSiblings |
P116799
|
FINISHED |
| Object | younger son |
—
|
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: younger son | Statement: [Ferdinand of Castile, Lord of Ledesma, relativePositionInSiblings, younger son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionInSiblings Context triple: [Ferdinand of Castile, Lord of Ledesma, relativePositionInSiblings, younger son]
-
A.
relativePositionInGroup
chosen
Indicates the spatial or ordered placement of an entity within a defined group relative to the other members of that group.
-
B.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
-
D.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
E.
positionInHierarchy
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:53 a.m.