Triple
T34525785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarch of the East Indies |
E886393
|
entity |
| Predicate | linkedToHistoricalSee |
P81077
|
FINISHED |
| Object | Goa |
—
|
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: Goa | Statement: [Patriarch of the East Indies, linkedToHistoricalSee, Goa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToHistoricalSee Context triple: [Patriarch of the East Indies, linkedToHistoricalSee, Goa]
-
A.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
B.
historicalSee
Indicates that one entity observed, encountered, or took visual notice of another entity in the past.
-
C.
includesHistoricSee
Indicates that something contains or encompasses a historically significant site, feature, or point of interest.
-
D.
otherHistoricSee
chosen
Indicates that an entity is associated with or linked to another historically significant site, event, or point of interest that can be seen or visited.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 1, 2026, 2:02 a.m.