Triple
T22430795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modern No. 20 |
E554492
|
entity |
| Predicate | hasTerminalStyle |
P1609
|
FINISHED |
| Object | flat unbracketed serifs |
—
|
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: flat unbracketed serifs | Statement: [Modern No. 20, hasTerminalStyle, flat unbracketed serifs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalStyle Context triple: [Modern No. 20, hasTerminalStyle, flat unbracketed serifs]
-
A.
has terminal type
Indicates that an entity is associated with a specific terminal type or category it belongs to.
-
B.
isTerminal
Indicates that an entity represents an endpoint or final state in a process, structure, or sequence, with no further continuation beyond it.
-
C.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
D.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
E.
hasTerminalShape
Indicates that one entity possesses or exhibits a particular terminal (end) shape defined 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a311b148190bdb752f3f067bb3f |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.