Triple
T988588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drexel University |
E21334
|
entity |
| Predicate | schoolColor |
P19185
|
FINISHED |
| Object | blue |
—
|
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: blue | Statement: [Drexel University, schoolColor, blue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolColor Context triple: [Drexel University, schoolColor, blue]
-
A.
hasSchoolColours
chosen
Indicates that an entity is associated with one or more official colours that represent it, typically in formal or symbolic contexts.
-
B.
teamColor
Indicates the association between a team and the color that represents or identifies it.
-
C.
schoolBoard
Indicates that an entity serves as or is governed by a school board responsible for overseeing educational policies and administration.
-
D.
schoolDistrict
Indicates that one entity is a school district that administers, oversees, or serves the other entity (such as a school or geographic area).
-
E.
partnerSchool
Indicates a formal collaborative relationship between two educational institutions, typically involving shared programs, resources, or exchange activities.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4a89a58819081a24b5b0a12f122 |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2abccbc8190a83af432f89eacf5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.