Triple
T25277490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise Banks |
E633738
|
entity |
| Predicate | resolvesConflict |
P23081
|
FINISHED |
| Object | international crisis with aliens |
—
|
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: international crisis with aliens | Statement: [Louise Banks, resolvesConflict, international crisis with aliens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolvesConflict Context triple: [Louise Banks, resolvesConflict, international crisis with aliens]
-
A.
conflictResolvedBy
chosen
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
B.
conflictResult
Indicates the outcome or consequence that arises from a particular conflict between entities.
-
C.
basedOnConflict
Indicates that one entity is derived from, influenced by, or structured around a particular conflict involving another entity.
-
D.
supportedConflict
Indicates that one party provided assistance, resources, or endorsement to a side involved in a conflict or dispute.
-
E.
wonConflict
Indicates that one entity has prevailed over another in a conflict, contest, or struggle.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:18 p.m.