Triple
T31490504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWV 86A |
E803391
|
entity |
| Predicate | linkedToWorkNumber |
P193315
|
FINISHED |
| Object | WWV 86B |
—
|
NE NERFINISHED |
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: WWV 86B | Statement: [WWV 86A, linkedToWorkNumber, WWV 86B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToWorkNumber Context triple: [WWV 86A, linkedToWorkNumber, WWV 86B]
-
A.
associatedNumber
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
B.
worksAsContactFor
Indicates that one entity serves as the designated contact person or liaison for another entity.
-
C.
worksNumber
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
-
D.
workNumberInKey
Indicates that a specific work or item is identified or referenced by a particular number used as a key in some cataloging or indexing system.
-
E.
hasWorkNumberType
Indicates that an entity’s work-related phone number is classified as a specific type (e.g., mobile, landline, extension).
- F. None of above. chosen
Provenance (4 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: April 30, 2026, 9:38 p.m.