Triple
T9698450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South 52nd Street |
E234712
|
entity |
| Predicate | hasDirectionalQualifier |
P72660
|
FINISHED |
| Object | South |
—
|
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: South | Statement: [South 52nd Street, hasDirectionalQualifier, South]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionalQualifier Context triple: [South 52nd Street, hasDirectionalQualifier, South]
-
A.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
B.
hasDirectionReference
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
C.
hasDirectionalSuffix
chosen
Indicates that something is associated with or marked by a suffix expressing direction or orientation.
-
D.
hasDirectionVariant
Indicates that one entity is a directional variant or orientation-specific form of another entity.
-
E.
hasQualifier
Indicates that one entity serves as a qualifier or modifier that further specifies or restricts the meaning or scope of another entity or statement.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d3d425c8190b652d84186b5ce9f |
completed | April 1, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.