Triple
T24213995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canton High School (Michigan) |
E600635
|
entity |
| Predicate | sharedCampusWith |
P4386
|
FINISHED |
| Object | Plymouth High School (Michigan) |
—
|
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: Plymouth High School (Michigan) | Statement: [Canton High School (Michigan), sharedCampusWith, Plymouth High School (Michigan)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedCampusWith Context triple: [Canton High School (Michigan), sharedCampusWith, Plymouth High School (Michigan)]
-
A.
sharesCampusWith
chosen
Indicates that two entities are located on or use the same campus or campus facilities.
-
B.
sharesCorridorWith
Indicates that two entities are located along or connected by the same corridor or passageway.
-
C.
sharesFacilityWith
Indicates that two entities use or have access to the same physical facility or location.
-
D.
sharesRoomWith
Indicates that two entities occupy or use the same room at the same time.
-
E.
sharesCollegialBodyWith
Indicates that two entities are members of, or participate together in, the same collegial body or collective decision-making group.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820679a881909483c2d49f16508a |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:57 p.m.