Triple
T30271194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagles |
E769801
|
entity |
| Predicate | locationOfUniversityRepresented |
P13918
|
FINISHED |
| Object | Baltimore, Maryland |
—
|
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: Baltimore, Maryland | Statement: [Eagles, locationOfUniversityRepresented, Baltimore, Maryland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfUniversityRepresented Context triple: [Eagles, locationOfUniversityRepresented, Baltimore, Maryland]
-
A.
universityLocatedIn
chosen
Indicates that a university is situated within or associated with a specific geographic location or administrative region.
-
B.
seatOfUniversity
Indicates that a location serves as the official seat or main campus of a university.
-
C.
boroughOfCollegeRepresented
Indicates that a specific borough of a college is officially represented by a particular person, group, or body.
-
D.
universityRepresentedIs
Indicates that one entity serves as the official representative or embodiment of a particular university.
-
E.
campusLocationOfParticipant
Indicates that a participant is located on or associated with a particular campus.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00b03a50a88190bfb95cdcfc6142a2 |
completed | May 10, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_6a00afe55f248190b2cb4c7e62cc3ffc |
completed | May 10, 2026, 4:18 p.m. |
Created at: April 29, 2026, 7:43 p.m.