Triple
T6555316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangkalan |
E152431
|
entity |
| Predicate | vehicleRegistrationCodeProvince |
P1173
|
FINISHED |
| Object | L (East Java, including Madura) |
—
|
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: L (East Java, including Madura) | Statement: [Bangkalan, vehicleRegistrationCodeProvince, L (East Java, including Madura)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleRegistrationCodeProvince Context triple: [Bangkalan, vehicleRegistrationCodeProvince, L (East Java, including Madura)]
-
A.
hasProvinceName
Indicates that an entity (such as a province or region) bears or is associated with a specific province name.
-
B.
vehicleRegistrationCode
chosen
Indicates the official registration identifier assigned to a vehicle, typically used for legal identification and record-keeping.
-
C.
provinceName
Indicates that a province entity is associated with its specific name as a textual label.
-
D.
teamProvinceOrState
Indicates that a team is located in, or associated with, a particular province or state.
-
E.
governingProvince
Indicates that one administrative unit or authority has official governing control over a specified province.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.