Triple
T38468421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luso |
E912638
|
entity |
| Predicate | isFormerNameOfProvincialCapital |
P49652
|
FINISHED |
| Object | Luena |
—
|
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: Luena | Statement: [Luso, isFormerNameOfProvincialCapital, Luena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormerNameOfProvincialCapital Context triple: [Luso, isFormerNameOfProvincialCapital, Luena]
-
A.
formerNameOfCapital
chosen
Indicates that one entity was the previous official name of a capital city before it was renamed.
-
B.
formerNameOfProvince
Indicates that one name was previously used as the official name of a province before being replaced by another name.
-
C.
capitalOfProvincePreviouslyLocatedOn
Indicates that an entity serves or served as the capital city of a province that was formerly situated in a specified location.
-
D.
isInFormerCapital
Indicates that an entity is located within a city that previously served as a capital but no longer holds that status.
-
E.
formerCapitalOf
Indicates that a place once served as the capital of another entity (such as a country or region) but no longer holds that status.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.