Triple
T27871948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oga Garra |
E704812
|
entity |
| Predicate | notablePatrons |
P29285
|
FINISHED |
| Object | smugglers |
—
|
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: smugglers | Statement: [Oga Garra, notablePatrons, smugglers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePatrons Context triple: [Oga Garra, notablePatrons, smugglers]
-
A.
hasNotablePatron
chosen
Indicates that an entity is significantly supported, sponsored, or championed by a distinguished or influential patron.
-
B.
historicalPatron
Indicates that one entity served as a patron or sponsor of another in a historical context, providing support, protection, or resources.
-
C.
notableDonor
Indicates that one entity is a significant or prominent donor to another entity, typically through substantial or noteworthy contributions.
-
D.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
-
E.
patron of
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: April 27, 2026, 6:25 p.m.