Triple
T5015353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinite Loop campus |
E112728
|
entity |
| Predicate | timePeriodAsMainHeadquartersStart |
P60856
|
FINISHED |
| Object | mid-1990s |
—
|
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: mid-1990s | Statement: [Infinite Loop campus, timePeriodAsMainHeadquartersStart, mid-1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodAsMainHeadquartersStart Context triple: [Infinite Loop campus, timePeriodAsMainHeadquartersStart, mid-1990s]
-
A.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
-
B.
focusPeriodStart
Indicates the point in time at which a specified focus period or interval begins.
-
C.
timeAsCapitalStart
Indicates the point in time when a location first became the capital of a political or administrative entity.
-
D.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
E.
headquartersLocationTime
Indicates the location where an entity’s headquarters is situated during a specified time period.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:35 p.m.