Triple
T30674026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Atlantis |
E780864
|
entity |
| Predicate | powersAssociatedWithTitle |
P180158
|
FINISHED |
| Object | superhuman strength |
—
|
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: superhuman strength | Statement: [King of Atlantis, powersAssociatedWithTitle, superhuman strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powersAssociatedWithTitle Context triple: [King of Atlantis, powersAssociatedWithTitle, superhuman strength]
-
A.
powersKnownAs
Indicates that an entity’s powers or abilities are referred to or recognized by a particular name or designation.
-
B.
authorizedByTitle
Indicates that an action or permission is granted based on a person’s role, position, or formal title rather than on individual identity.
-
C.
parliamentaryAffiliationOfTitleholders
Indicates the parliamentary group, party, or affiliation associated with the holders of a given title.
-
D.
notableOfficerTitle
Indicates that an entity holds or is associated with a particularly distinguished or noteworthy officer position or title.
-
E.
officeHoldersShareTitleWith
Indicates that two or more office holders possess the same official title or position.
- F. None of above. chosen
Provenance (4 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 29, 2026, 8:32 p.m.