Triple
T361642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LU |
E7866
|
entity |
| Predicate | numericCodeForSameEntity |
P3732
|
FINISHED |
| Object | 442 |
—
|
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: 442 | Statement: [LU, numericCodeForSameEntity, 442]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericCodeForSameEntity Context triple: [LU, numericCodeForSameEntity, 442]
-
A.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
B.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
relatedCode
Indicates that one code is associated with, linked to, or otherwise contextually connected to another code.
-
D.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
E.
isUniqueWithinSystem
Indicates that an entity exists only once and has no duplicates within the defined system or scope.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebce64c88190a0a8edcc7095f78b |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95c843c8190b2aba9af6e869ba1 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.