Triple
T29397732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tube map |
E745548
|
entity |
| Predicate | usesLayoutStyle |
P30520
|
FINISHED |
| Object | topological layout |
—
|
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: topological layout | Statement: [Tube map, usesLayoutStyle, topological layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLayoutStyle Context triple: [Tube map, usesLayoutStyle, topological layout]
-
A.
usesGridBasedLayout
Indicates that an entity arranges its elements or content according to a structured grid-based layout system.
-
B.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
C.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
-
D.
usesAsStyleOf
chosen
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
-
E.
usesCodePageLayout
Indicates that one entity arranges or interprets character data according to the code page layout defined or provided by 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 2:47 p.m.