Triple
T5196568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish vehicle registration plates |
E117287
|
entity |
| Predicate | includeCode |
P5026
|
FINISHED |
| Object | WA |
—
|
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: WA | Statement: [Polish vehicle registration plates, includeCode, WA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeCode Context triple: [Polish vehicle registration plates, includeCode, WA]
-
A.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
-
B.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
C.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
D.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
E.
relatedCode
chosen
Indicates that one code is associated with, linked to, or otherwise contextually connected to another code.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.