Triple
T5613722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSM |
E147424
|
entity |
| Predicate | numericCodeRelation |
P508
|
FINISHED |
| Object | 882 |
—
|
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: 882 | Statement: [WSM, numericCodeRelation, 882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericCodeRelation Context triple: [WSM, numericCodeRelation, 882]
-
A.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
B.
languageCodeRelation
Indicates a relationship where one entity is associated with, identified by, or mapped to a specific language code of another entity.
-
C.
relatedCodeSet
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
D.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
E.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
- 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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c021226cf88190b70b4b51eb5b4144 |
completed | March 22, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.