Triple
T9924732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six Months in Mexico |
E187891
|
entity |
| Predicate | durationOfStayDescribed |
P50746
|
FINISHED |
| Object | six months |
—
|
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: six months | Statement: [Six Months in Mexico, durationOfStayDescribed, six months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: durationOfStayDescribed Context triple: [Six Months in Mexico, durationOfStayDescribed, six months]
-
A.
reasonForStay
Indicates the underlying cause, purpose, or circumstance that explains why an entity remains or is staying in a particular place or situation.
-
B.
residencyDuration
chosen
Indicates the length of time an entity has continuously resided or stayed in a particular place or jurisdiction.
-
C.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
durationOfAffliction
Indicates the length of time that an affliction or condition persists for an entity.
-
E.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
- 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_69ca82b22a688190b52c75bd48429c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb598651081908286763ff56ba57c |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.