Triple
T16408967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Maine |
E398508
|
entity |
| Predicate | relationshipToAlly |
P123314
|
FINISHED |
| Object | mentor |
—
|
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: mentor | Statement: [Jackson Maine, relationshipToAlly, mentor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToAlly Context triple: [Jackson Maine, relationshipToAlly, mentor]
-
A.
formerAllyOf
Indicates that an entity was once an ally of another entity but that alliance has since ended.
-
B.
allianceOrRivalry
Indicates a relationship where entities are either cooperating as allies or competing as rivals, capturing both partnership and opposition dynamics.
-
C.
hasPoliticalAlly
Indicates that one entity supports and cooperates with another in a political context, treating them as an ally in political activities or objectives.
-
D.
allianceStatus
Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
-
E.
sometimesAllyOf
Indicates that one entity is an ally of another in some situations or periods, but not consistently or universally.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32871bce08190addd637413473c87 |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.