Triple
T25177661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Font Bureau |
E630490
|
entity |
| Predicate | servesUseCase |
P52084
|
FINISHED |
| Object | print design |
—
|
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: print design | Statement: [Font Bureau, servesUseCase, print design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesUseCase Context triple: [Font Bureau, servesUseCase, print design]
-
A.
servesUse
Indicates that one entity is used by or functions to serve the purpose or needs of another entity.
-
B.
servesUsers
Indicates that an entity provides services, functionality, or benefits to one or more users.
-
C.
serviceUseCase
chosen
Indicates that an entity is used as a service to fulfill or support a particular use case or functional scenario.
-
D.
hasServingUse
Indicates that something is used or intended to be used for serving (e.g., food, drink, or portions).
-
E.
servesFeature
Indicates that one entity provides or makes available a particular feature or functionality to 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 12:34 p.m.