Triple
T25812263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIJJ |
E650143
|
entity |
| Predicate | isFormerCodeFor |
P54575
|
FINISHED |
| Object | JOG |
—
|
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: JOG | Statement: [WIJJ, isFormerCodeFor, JOG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormerCodeFor Context triple: [WIJJ, isFormerCodeFor, JOG]
-
A.
hasFormerCode
chosen
Indicates that an entity was previously identified or referenced by an earlier code that is no longer current.
-
B.
isFormerEntity
Indicates that an entity previously held a particular status, role, or identity but no longer does so.
-
C.
isOfficialCodeFor
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
-
D.
containsFormerlyNamed
Indicates that one entity currently contains another entity that was previously known by a different name.
-
E.
predecessorCode
Indicates that one code directly precedes another code in a defined sequence or versioning order.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c5b8048190a116f2b0521e9814 |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 7:11 a.m.