Triple
T5015354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinite Loop campus |
E112728
|
entity |
| Predicate | timePeriodAsMainHeadquartersEnd |
P35259
|
FINISHED |
| Object | late 2010s |
—
|
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: late 2010s | Statement: [Infinite Loop campus, timePeriodAsMainHeadquartersEnd, late 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodAsMainHeadquartersEnd Context triple: [Infinite Loop campus, timePeriodAsMainHeadquartersEnd, late 2010s]
-
A.
timePeriodAsSeatOfGovernmentEnd
Indicates the point in time when a particular location ceases to serve as the seat of government for an entity.
-
B.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
C.
governedPeriodEnd
Indicates the point in time at which a governing authority’s control or jurisdiction over something comes to an end.
-
D.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732e0b848190858407920e7aefd0 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.