Triple
T38358937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Esses |
E1046414
|
entity |
| Predicate | hasDirectionPattern |
P74179
|
FINISHED |
| Object | left-right sequence |
—
|
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: left-right sequence | Statement: [The Esses, hasDirectionPattern, left-right sequence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionPattern Context triple: [The Esses, hasDirectionPattern, left-right sequence]
-
A.
hasDirectionPatterns
chosen
Indicates that one entity exhibits or is associated with specific directional patterns in its behavior, structure, or configuration relative to another entity or context.
-
B.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
C.
hasDirectionInName
Indicates that the entity’s name explicitly contains a directional term (e.g., north, south, east, west, or similar).
-
D.
hasDirectionCode
Indicates that something is associated with a specific standardized code representing its direction or orientation.
-
E.
hasDirectionVariant
Indicates that one entity is a directional variant or orientation-specific form of 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:31 p.m.