Triple
T15511986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothar Meyer periodic table |
E368730
|
entity |
| Predicate | hasVisualizationForm |
P11599
|
FINISHED |
| Object | table |
—
|
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: table | Statement: [Lothar Meyer periodic table, hasVisualizationForm, table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisualizationForm Context triple: [Lothar Meyer periodic table, hasVisualizationForm, table]
-
A.
visualizedIn
Indicates that something is represented or depicted within a particular visual medium, view, or visualization.
-
B.
visualForm
chosen
Indicates the visual appearance, shape, or structural pattern that characterizes how something looks.
-
C.
visualizationMethod
Indicates the technique or approach used to visually represent data, information, or concepts.
-
D.
hasVisualIndicator
Indicates that an entity is associated with some form of visual cue or marker that signals its status, condition, or presence.
-
E.
formsVisualCompositionWith
Indicates that one entity participates together with another in creating or constituting a shared visual composition or arrangement.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04030c0208190a1931ea130075603 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:56 a.m.