Triple
T36684448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidigueira |
E905777
|
entity |
| Predicate | historicalTitleHolder |
P113994
|
FINISHED |
| Object | Vasco da Gama |
—
|
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: Vasco da Gama | Statement: [Vidigueira, historicalTitleHolder, Vasco da Gama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTitleHolder Context triple: [Vidigueira, historicalTitleHolder, Vasco da Gama]
-
A.
titleHolders
chosen
Indicates that one or more entities currently or formerly hold a specified title, position, or honor.
-
B.
foundingTitleHolder
Indicates that the subject is the original or inaugural holder of a particular title, position, or office.
-
C.
isHistoricTitle
Indicates that a given title or designation was used in the past and is no longer current, but is retained for historical reference.
-
D.
titleHolderServedAs
Indicates that the entity holding a particular title also performed the role or function associated with that title.
-
E.
traditionalTitleHolder
Indicates that one entity holds a customary or historically established title or rank in relation to 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01487b73488190954eb5143e6f246e |
completed | May 11, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a0145210ae481908da59b02efdbc397 |
completed | May 11, 2026, 2:55 a.m. |
Created at: May 3, 2026, 4:12 p.m.