Triple
T18180696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Lost Family |
E435271
|
entity |
| Predicate | typicalSeparationDuration |
P100488
|
FINISHED |
| Object | decades |
—
|
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: decades | Statement: [Long Lost Family, typicalSeparationDuration, decades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSeparationDuration Context triple: [Long Lost Family, typicalSeparationDuration, decades]
-
A.
separationPeriod
chosen
Indicates the duration or interval of time during which two entities are separated from each other.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
separatedUntil
Indicates that two entities remain apart or not in contact up to a specified time or condition.
-
D.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
E.
typeOfSeparation
Indicates the specific manner or category of separation that exists or occurred between entities.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffa75a081908dad0dcbd736172d |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.