Triple
T35704439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hearst College |
E1031676
|
entity |
| Predicate | usedAsBacklotLocation |
P7951
|
FINISHED |
| Object | actual Southern California college campuses (production) |
—
|
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: actual Southern California college campuses (production) | Statement: [Hearst College, usedAsBacklotLocation, actual Southern California college campuses (production)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBacklotLocation Context triple: [Hearst College, usedAsBacklotLocation, actual Southern California college campuses (production)]
-
A.
hasBacklot
chosen
Indicates that one entity possesses or includes a backlot area associated with it.
-
B.
hasGardenUse
Indicates that something is used for, or serves a particular function within, a garden.
-
C.
homeGroundUsedFor
Indicates that a particular venue or stadium is used as the designated home ground for a team, club, or organization.
-
D.
hasCourtyardUse
Indicates that one entity is permitted or designated to use the courtyard of another entity.
-
E.
usedAsImperialGardenUntil
Indicates that something served the function of an imperial garden up to a specified point in time.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:05 p.m.