Triple
T4326154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JointGrid |
E96637
|
entity |
| Predicate | visualLayout |
P11599
|
FINISHED |
| Object | one central joint axis with two marginal axes |
—
|
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: one central joint axis with two marginal axes | Statement: [JointGrid, visualLayout, one central joint axis with two marginal axes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualLayout Context triple: [JointGrid, visualLayout, one central joint axis with two marginal axes]
-
A.
visualForm
chosen
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
-
B.
visualElements
Indicates that one entity contains, uses, or is characterized by specific visual components or graphical features associated with another entity.
-
C.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
D.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
-
E.
printLayout
Indicates that one entity arranges and formats content for physical or virtual printing according to a specified layout.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3513020f481909ff2fec3934f3002 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.