Triple
T33946276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby New York |
E870297
|
entity |
| Predicate | previousHomeGroundLocation |
P114909
|
FINISHED |
| Object | Fordham University |
—
|
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: Fordham University | Statement: [Rugby New York, previousHomeGroundLocation, Fordham University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHomeGroundLocation Context triple: [Rugby New York, previousHomeGroundLocation, Fordham University]
-
A.
previousHomeGroundLocatedIn
chosen
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
B.
primaryHomeGroundNot
Indicates that the specified location is explicitly not the entity’s primary home ground.
-
C.
previousHomeFieldUse
Indicates that one entity was formerly used as the home field or primary venue for another entity before a later change.
-
D.
homeFieldLocation
Indicates the location where an entity’s primary or home field, venue, or playing ground is situated.
-
E.
laterHomeGround
Indicates that one entity became the home ground of the other at a later time, after some previous home ground or earlier period.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 1, 2026, 1:49 a.m.