Triple
T38369161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot (Community) |
E892530
|
entity |
| Predicate | locationOfFictionalCollege |
P195618
|
FINISHED |
| Object | Greendale, Colorado |
E810887
|
NE 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: Greendale, Colorado | Statement: [Pilot (Community), locationOfFictionalCollege, Greendale, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFictionalCollege Context triple: [Pilot (Community), locationOfFictionalCollege, Greendale, Colorado]
-
A.
universityLocatedIn
Indicates that a university is situated within or associated with a specific geographic location or administrative region.
-
B.
hasFictionalSchool
Indicates that an entity is associated with or contains a school that exists only within a fictional or imaginary context.
-
C.
collegeLocation
chosen
Indicates the geographical place where a college is situated or based.
-
D.
hasCampusOn
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
E.
cityCampusServes
Indicates that a city campus provides services, resources, or support to a particular population, area, or institution.
- F. None of above.
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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a45eddce9e88190875966cdd934ffaa |
completed | July 2, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.