Triple
T17044488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North 21st Street |
E413528
|
entity |
| Predicate | hasGeneralUse |
P27871
|
FINISHED |
| Object | urban traffic thoroughfare |
—
|
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: urban traffic thoroughfare | Statement: [North 21st Street, hasGeneralUse, urban traffic thoroughfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralUse Context triple: [North 21st Street, hasGeneralUse, urban traffic thoroughfare]
-
A.
hasGeneralPurpose
chosen
Indicates that one entity serves as the broad, overarching function, role, or intended use of another entity.
-
B.
usedAsGeneral
Indicates that an entity served in the role or capacity of a general, typically as a high-ranking military commander.
-
C.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
D.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
E.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9c112c81908232dc6908d831cf |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.