Triple
T28791164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Coast Conference |
E726956
|
entity |
| Predicate | operatedPrimarilyDuring |
P802
|
FINISHED |
| Object | first half of the 20th century |
—
|
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 half of the 20th century | Statement: [Pacific Coast Conference, operatedPrimarilyDuring, first half of the 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedPrimarilyDuring Context triple: [Pacific Coast Conference, operatedPrimarilyDuring, first half of the 20th century]
-
A.
operatedDuring
chosen
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
B.
operatedInYear
Indicates that an entity was actively operating or functioning during a specified year.
-
C.
historicallyOperatedOn
Indicates that an entity has, at some point in the past, performed an operation or action upon another entity.
-
D.
mainlyRecordedDuring
Indicates that an event, activity, or phenomenon was predominantly documented or captured within a specific time period or context.
-
E.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: April 28, 2026, 6:23 a.m.