Triple
T25949263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genii |
E653924
|
entity |
| Predicate | relationshipWithAtlantis |
P194737
|
FINISHED |
| Object | uneasy alliance |
—
|
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: uneasy alliance | Statement: [Genii, relationshipWithAtlantis, uneasy alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithAtlantis Context triple: [Genii, relationshipWithAtlantis, uneasy alliance]
-
A.
roleInAtlantis
Indicates that an entity holds or is assigned a specific role, position, or function within the context of Atlantis.
-
B.
relationshipToPetra
Indicates the specific type of relationship or connection that one entity has to Petra.
-
C.
poseidonRelation
Indicates a mythological or symbolic relationship involving Poseidon, such as kinship, patronage, or influence over another entity.
-
D.
hasUnderwaterCity
Indicates that one entity possesses, controls, or contains a city located underwater.
-
E.
relationshipWithProspero
Indicates that one entity has a specified type of interpersonal or narrative relationship with Prospero.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: April 22, 2026, 8:43 a.m.