Triple
T37103713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dongsi South Street |
E918778
|
entity |
| Predicate | hasDirectionStart |
P200291
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Dongsi South Street, hasDirectionStart, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionStart Context triple: [Dongsi South Street, hasDirectionStart, north]
-
A.
hasDirectionInName
Indicates that the entity’s name explicitly contains a directional term (e.g., north, south, east, west, or similar).
-
B.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
C.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
D.
hasDirectionReference
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
E.
directionFromStart
Indicates the orientation or path taken moving outward from a defined starting point toward another location or object.
- F. None of above. chosen
Provenance (4 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
| PDg | Predicate description generation | batch_69ff7eb638c48190aeca7b85b9b698ab |
completed | May 9, 2026, 6:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.