Triple
T30030786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gies Foundation |
E763009
|
entity |
| Predicate | hasNamedRelationshipWith |
P136469
|
FINISHED |
| Object | Gies College of Business |
—
|
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: Gies College of Business | Statement: [Gies Foundation, hasNamedRelationshipWith, Gies College of Business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedRelationshipWith Context triple: [Gies Foundation, hasNamedRelationshipWith, Gies College of Business]
-
A.
hasRelationships
Indicates that an entity is connected to one or more other entities through specified types of relationships.
-
B.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
C.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
D.
hasKeyRelationship
Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies another entity.
-
E.
namedForRelationship
chosen
Indicates that one entity serves as the namesake or source of the name for another entity.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 29, 2026, 6:49 p.m.