Triple
T11909706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Johnston |
E283360
|
entity |
| Predicate | designClassification |
P58468
|
FINISHED |
| Object | humanist sans-serif |
—
|
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: humanist sans-serif | Statement: [New Johnston, designClassification, humanist sans-serif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designClassification Context triple: [New Johnston, designClassification, humanist sans-serif]
-
A.
designClass
Indicates that one entity is the design or blueprint class from which the other entity is derived or instantiated.
-
B.
designCategory
chosen
Indicates that one entity is classified under a particular design-related category or type.
-
C.
classificationAccordingTo
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
D.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
E.
designatorCategory
Indicates the classification or type assigned to a designator within a given system or context.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e5278eb081909a7ecfe38beeeda9 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.