Triple
T21805200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1903 New Orleans reunion |
E538331
|
entity |
| Predicate | publicSpaceUse |
P61443
|
FINISHED |
| Object | downtown New Orleans streets |
—
|
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: downtown New Orleans streets | Statement: [1903 New Orleans reunion, publicSpaceUse, downtown New Orleans streets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicSpaceUse Context triple: [1903 New Orleans reunion, publicSpaceUse, downtown New Orleans streets]
-
A.
publicSpacesUsed
chosen
Indicates that certain public spaces are being utilized or occupied for a particular purpose or activity.
-
B.
spaceUsage
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
-
C.
totalSpace
Indicates the overall amount of space or capacity available or occupied by an entity or within a given context.
-
D.
gridUsage
Indicates how much and in what way an entity consumes or relies on a shared grid-based resource, such as an electrical or data grid.
-
E.
usesSpace
Indicates that one entity occupies, consumes, or makes use of physical or conceptual space associated with 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07801fa8081909098d00947bf8f7f |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.