Triple
T38160016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Univers |
E952990
|
entity |
| Predicate | designerOfDigitization |
P200539
|
FINISHED |
| Object | Linotype Design Studio |
—
|
NE NERFINISHED |
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: Linotype Design Studio | Statement: [Univers, designerOfDigitization, Linotype Design Studio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designerOfDigitization Context triple: [Univers, designerOfDigitization, Linotype Design Studio]
-
A.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
B.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
C.
designerAlias
Indicates that one name or label is used as an alternative alias for a designer.
-
D.
designSucceededBy
Indicates that one design is followed or replaced by another design in a temporal or version sequence.
-
E.
designerOccupation
Indicates that one entity serves as the professional designer or design specialist for another entity.
- F. None of above. chosen
Provenance (4 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
| PDg | Predicate description generation | batch_69ff935f48808190aa6f4834f59d45b8 |
completed | May 9, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.