Triple
T768946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Tree |
E16236
|
entity |
| Predicate | onlinePresence |
P18972
|
FINISHED |
| Object | featured on Stanford Band and student-run social media |
—
|
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: featured on Stanford Band and student-run social media | Statement: [Stanford Tree, onlinePresence, featured on Stanford Band and student-run social media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlinePresence Context triple: [Stanford Tree, onlinePresence, featured on Stanford Band and student-run social media]
-
A.
globalPresence
Indicates that an entity operates, is represented, or has a significant footprint across multiple countries or world regions.
-
B.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
C.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
-
D.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
-
E.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
- F. None of above. chosen
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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a701e584819095905cf74d33e11c |
completed | March 1, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5a35c68819082429755c046e9a7 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.