Triple
T24431029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liara T'Soni |
E616001
|
entity |
| Predicate | roleInMassEffect2 |
P156101
|
FINISHED |
| Object | information broker on Illium |
—
|
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: information broker on Illium | Statement: [Liara T'Soni, roleInMassEffect2, information broker on Illium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMassEffect2 Context triple: [Liara T'Soni, roleInMassEffect2, information broker on Illium]
-
A.
roleInCallOfDutyModernWarfare2
Indicates that an entity has a specific role or involvement in the video game "Call of Duty: Modern Warfare 2."
-
B.
roleInOverwatch2
Indicates the specific function or position an entity holds within the context of Overwatch 2 (such as tank, damage, or support role).
-
C.
roleOnGalactica
Indicates the specific position, duty, or function an entity holds aboard the Battlestar Galactica.
-
D.
roleInAlienCovenant
Indicates that an entity has a role or participation in the film "Alien: Covenant."
-
E.
roleInElysium
Indicates that an entity holds a specific role, position, or function within the context of Elysium.
- 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_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. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.