Triple
T7907926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millner |
E183622
|
entity |
| Predicate | belongsToOnomasticType |
P78011
|
FINISHED |
| Object | trade name |
—
|
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: trade name | Statement: [Millner, belongsToOnomasticType, trade name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToOnomasticType Context triple: [Millner, belongsToOnomasticType, trade name]
-
A.
hasOnomasticField
Indicates a relationship where something is associated with a specific onomastic field, i.e., a domain or category related to names or naming conventions.
-
B.
belongsToNamingTradition
chosen
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
C.
belongsToSystemType
Indicates that one entity is classified under, or is a member of, a particular system type.
-
D.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
-
E.
hasEndonymType
Indicates the specific type or category of an entity’s endonym (its name in its own language or local usage).
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a59de00819099f1ce02bb469e75 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.