Triple
T30074116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RE |
E764268
|
entity |
| Predicate | codeOn |
P168413
|
FINISHED |
| Object | Austrian vehicle registration plates |
—
|
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: Austrian vehicle registration plates | Statement: [RE, codeOn, Austrian vehicle registration plates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeOn Context triple: [RE, codeOn, Austrian vehicle registration plates]
-
A.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
B.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
C.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
D.
designCode
Indicates that one entity creates, specifies, or defines the design or coding scheme used by another entity.
-
E.
codeNature
Indicates that one entity characterizes or specifies the type, category, or inherent nature of another entity, often in a coded or standardized form.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d3b9b0c81909091a13dcf2b63b7 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:01 p.m.