Triple
T17854264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barangay Sta. Cruz |
E445888
|
entity |
| Predicate | isInCountryCapitalRegion |
P66890
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Barangay Sta. Cruz, isInCountryCapitalRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCountryCapitalRegion Context triple: [Barangay Sta. Cruz, isInCountryCapitalRegion, true]
-
A.
isInStateCapitalRegionOf
Indicates that one entity is located within the capital region of the state to which the other entity belongs.
-
B.
locatedInNationCapitalRegion
chosen
Indicates that an entity is situated within the capital region of a specific nation.
-
C.
hasCapitalRegionRelation
Indicates a relationship where one entity serves as the capital region or administrative capital area of another entity.
-
D.
containsCapitalOf
Indicates that one location geographically includes the city that serves as the capital of another region or entity.
-
E.
locatedInCountryCapitalSystem
Indicates that an entity is situated in the capital city of a specified country within a country–capital relationship system.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49001d8b881908c8d4efc3d7ff04f |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.