Triple
T26168263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UM |
E654319
|
entity |
| Predicate | hasNumericCodeRelated |
P508
|
FINISHED |
| Object | 581 |
—
|
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: 581 | Statement: [UM, hasNumericCodeRelated, 581]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumericCodeRelated Context triple: [UM, hasNumericCodeRelated, 581]
-
A.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
B.
numericCompanionCode
Indicates that one entity is associated with another through a specific numeric companion code used to link or reference them.
-
C.
hasCodeLetters
Indicates that an entity is associated with, or represented by, a specific sequence of letters used as its code or identifier.
-
D.
hasStandardCode
Indicates that an entity is associated with a recognized standard code that formally identifies or classifies it.
-
E.
hasParentCode
Indicates that an entity is associated with a parent code from which it is derived or to which it is hierarchically linked.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 26, 2026, 8:33 p.m.