Triple
T27194926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIZ |
E683573
|
entity |
| Predicate | codeForProvince |
P99880
|
FINISHED |
| Object | Rizal |
—
|
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: Rizal | Statement: [RIZ, codeForProvince, Rizal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeForProvince Context triple: [RIZ, codeForProvince, Rizal]
-
A.
hasProvincialCode
chosen
Indicates that an entity is associated with a specific provincial code that identifies its province or administrative region.
-
B.
cityCode
Indicates the standardized code that uniquely identifies a particular city.
-
C.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
D.
codeForSovereignState
Indicates that an entity serves as a code or coded identifier that officially represents a particular sovereign state.
-
E.
adminProvince
Indicates that one entity serves as the administrative province or primary provincial jurisdiction for another entity.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625aebd0081908349ebb1e7f380e9 |
completed | May 2, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:33 a.m.