Triple
T250545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baybayin |
E5135
|
entity |
| Predicate | hasDirectionality |
P2264
|
FINISHED |
| Object | horizontal |
—
|
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: horizontal | Statement: [Baybayin, hasDirectionality, horizontal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionality Context triple: [Baybayin, hasDirectionality, horizontal]
-
A.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
B.
hasWritingDirection
chosen
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
-
C.
directed
Indicates that one entity served as the director or guiding authority responsible for overseeing and controlling the actions or production involving another entity.
-
D.
hasStripeOrientation
Indicates the directional arrangement or alignment of stripes present on an entity.
-
E.
hasCommuterOrientation
Indicates that an entity is designed or intended primarily for use by commuters, emphasizing suitability for regular travel between home and work or study.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.