Triple
T25525837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sea Robbers |
E639772
|
entity |
| Predicate | foundedAsNicknameFor |
P38200
|
FINISHED |
| Object | Orlando Pirates F.C. |
—
|
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: Orlando Pirates F.C. | Statement: [The Sea Robbers, foundedAsNicknameFor, Orlando Pirates F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsNicknameFor Context triple: [The Sea Robbers, foundedAsNicknameFor, Orlando Pirates F.C.]
-
A.
nicknamedFor
chosen
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
B.
usedAsNamesakeFor
Indicates that one entity serves as the source or inspiration for the name given to another entity.
-
C.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
D.
foundedAsCurrentName
Indicates that an entity was originally founded under the same name it currently has, without having undergone a name change.
-
E.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 3:10 p.m.