Triple
T27851030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gantt chart |
E703951
|
entity |
| Predicate | representedOnAxis |
P126238
|
FINISHED |
| Object | time on horizontal axis |
—
|
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: time on horizontal axis | Statement: [Gantt chart, representedOnAxis, time on horizontal axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedOnAxis Context triple: [Gantt chart, representedOnAxis, time on horizontal axis]
-
A.
yAxisRepresents
Indicates that the y-axis in a chart or graph corresponds to and measures a particular variable, quantity, or category.
-
B.
coordinateAxis
Indicates that one entity serves as a reference axis or directional basis for positioning, measuring, or orienting another entity in a coordinate system.
-
C.
relationshipWithAxis
chosen
Indicates a specified way in which something is oriented, aligned, or otherwise related with respect to a particular axis.
-
D.
visualAxisRelation
Indicates a spatial relationship defined by the alignment or orientation of one entity relative to another along a line of sight or visual axis.
-
E.
axisWith
Indicates that one entity serves as or lies along a principal axis in relation to 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 6:11 p.m.