Triple
T10357587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarō |
E244039
|
entity |
| Predicate | oftenIndicatesBirthOrder |
P20593
|
FINISHED |
| Object | first 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: first son | Statement: [Tarō, oftenIndicatesBirthOrder, first son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenIndicatesBirthOrder Context triple: [Tarō, oftenIndicatesBirthOrder, first son]
-
A.
positionInFamilyBirthOrder
chosen
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
B.
hasTypicalBirthPeriod
Indicates the usual or characteristic time span during which the birth of an entity typically occurs.
-
C.
isFrequently
Indicates that an action, state, or relationship occurs often or with high regularity between the related entities.
-
D.
positionInLineOfSuccessionAtBirth
Indicates the ordinal place an individual held in a defined line of succession at the moment of their birth.
-
E.
birthStatus
Indicates the condition or circumstances of an entity’s birth, such as whether and how it was born.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9563ea48190b8702b3ef497ed9a |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:58 a.m.