Triple
T16011759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcatraz |
E388351
|
entity |
| Predicate | predecessorInSuit |
P121360
|
FINISHED |
| Object | Prophet |
—
|
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: Prophet | Statement: [Alcatraz, predecessorInSuit, Prophet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorInSuit Context triple: [Alcatraz, predecessorInSuit, Prophet]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorInRole
Indicates that one entity previously held a particular role or position that was later occupied by another entity.
-
C.
predecessorAsHeir
Indicates that one entity previously held the status of heir before being succeeded by another in that role.
-
D.
predecessorAsClaimant
Indicates that one entity previously held the status or role of claimant before another entity in a succession or sequence of claims.
-
E.
bearerPredecessor
Indicates that one entity previously held a role, title, or position that is now held by another entity, establishing a predecessor-successor relationship between them.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e185879c10819080a18e24969b5a6d |
completed | April 17, 2026, 12:57 a.m. |
Created at: April 10, 2026, 4:55 a.m.