Triple
T33230135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Nueva Segovia |
E850670
|
entity |
| Predicate | originalSeeCity |
P186243
|
FINISHED |
| Object | Nueva Segovia (Lal-lo, Cagayan) |
E1401396
|
NE 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: Nueva Segovia (Lal-lo, Cagayan) | Statement: [Diocese of Nueva Segovia, originalSeeCity, Nueva Segovia (Lal-lo, Cagayan)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSeeCity Context triple: [Diocese of Nueva Segovia, originalSeeCity, Nueva Segovia (Lal-lo, Cagayan)]
-
A.
coSeeCity
Indicates that two or more entities jointly see or observe the same city.
-
B.
seeCityCountry
Indicates that an entity observes or views a city together with its associated country.
-
C.
cityOfSee
chosen
Indicates the city in which a particular episcopal see (bishopric or diocesan seat) is located.
-
D.
secondarySeeCity
Indicates that an entity has a secondary or less prominent association with a particular city.
-
E.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
- F. None of above.
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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a02ff7de1d881909c29729f2a771381 |
completed | May 12, 2026, 10:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352fda48b88190838492c5676ae5b6 |
completed | June 19, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_6a02fd1c45c48190bf9dbd91acaeee9f |
completed | May 12, 2026, 10:12 a.m. |
Created at: May 1, 2026, 1:30 a.m.