Triple
T28267767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Tree Hill |
E712752
|
entity |
| Predicate | notableLocationInStory |
P15715
|
FINISHED |
| Object | Tree Hill High School |
—
|
NE NERFINISHED |
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: Tree Hill High School | Statement: [One Tree Hill, notableLocationInStory, Tree Hill High School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLocationInStory Context triple: [One Tree Hill, notableLocationInStory, Tree Hill High School]
-
A.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notableLocationFeatured
chosen
Indicates that a particular location is prominently highlighted or showcased in relation to the subject.
-
C.
notableLocationDocumented
Indicates that a specific location associated with an entity is recorded or documented as notable in some source or reference.
-
D.
notableGameLocation
Indicates that a particular place is recognized as a significant or prominent location within a game.
-
E.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a00b479c1588190af6e0698b7f8d7f7 |
completed | May 10, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_6a00b4158260819087d0cfad8b18cef4 |
completed | May 10, 2026, 4:36 p.m. |
Created at: April 27, 2026, 11:15 p.m.