Triple
T33731600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unimark International |
E864288
|
entity |
| Predicate | typographyPreference |
P42388
|
FINISHED |
| Object | Helvetica |
E864291
|
NE 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: Helvetica | Statement: [Unimark International, typographyPreference, Helvetica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typographyPreference Context triple: [Unimark International, typographyPreference, Helvetica]
-
A.
typographicPreference
Indicates a preferred typographic style or setting used for presenting or formatting content.
-
B.
typographicPhilosophy
Indicates a relationship where an entity’s approach, principles, or theory concerning typography and its use is specified.
-
C.
hasTypography
chosen
Indicates that one entity uses, is associated with, or is characterized by a particular typographic style, font, or text layout.
-
D.
textTypePreferred
Indicates that one entity has a preferred or favored type or category of text in relation to another entity.
-
E.
typographicRole
Indicates the specific typographic function or role that an element plays within written or printed content.
- F. None of above.
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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c7f93c08190a76890d51f4e13bd |
completed | June 20, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:44 a.m.