Triple
T27555223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aguilar v. Felton |
E695616
|
entity |
| Predicate | locationOfProgram |
P126496
|
FINISHED |
| Object | New York City |
—
|
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: New York City | Statement: [Aguilar v. Felton, locationOfProgram, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfProgram Context triple: [Aguilar v. Felton, locationOfProgram, New York City]
-
A.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
B.
hasProgramLocation
chosen
Indicates that a program, event, or activity takes place at or is associated with a specific location.
-
C.
positionInProgram
Indicates the specific place or order that something occupies within a larger program or sequence of program elements.
-
D.
binaryLocation
Indicates that one entity is the physical or logical location where another binary or executable artifact resides.
-
E.
locationOfCommand
Indicates that a specified place or facility serves as the site from which a particular command or authority is exercised.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: April 27, 2026, 1:36 p.m.