Triple
T24431188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashley Williams |
E616004
|
entity |
| Predicate | loyaltyMissionInMassEffect3 |
P104367
|
FINISHED |
| Object | Priority: Horizon |
—
|
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: Priority: Horizon | Statement: [Ashley Williams, loyaltyMissionInMassEffect3, Priority: Horizon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyMissionInMassEffect3 Context triple: [Ashley Williams, loyaltyMissionInMassEffect3, Priority: Horizon]
-
A.
loyaltyGoal
Indicates that one entity has the objective or commitment to remain faithful, supportive, or devoted to another entity or cause.
-
B.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
C.
loyaltyAlliance
Indicates a committed, supportive alliance in which one party maintains steadfast loyalty to another.
-
D.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
E.
loyaltyRevealedIn
chosen
Indicates that an entity’s loyalty becomes evident or is demonstrated through a particular situation, action, or context.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29782a4a0819087cb7ba399371520 |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.