Triple
T17672418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydian alphabet |
E440554
|
entity |
| Predicate | directionVariants |
P61247
|
FINISHED |
| Object | boustrophedon (rare or early examples) |
—
|
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: boustrophedon (rare or early examples) | Statement: [Lydian alphabet, directionVariants, boustrophedon (rare or early examples)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionVariants Context triple: [Lydian alphabet, directionVariants, boustrophedon (rare or early examples)]
-
A.
hasDirectionVariant
chosen
Indicates that one entity is a directional variant or orientation-specific form of another entity.
-
B.
hasDirectionVariability
Indicates that the direction associated with an entity or process is not fixed but varies over time, space, or conditions.
-
C.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f69b11c8190b09add33f81776b3 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.