Triple
T34475629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halyard Mission |
E885023
|
entity |
| Predicate | involvedLocalResistance |
P195157
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Halyard Mission, involvedLocalResistance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedLocalResistance Context triple: [Halyard Mission, involvedLocalResistance, true]
-
A.
resistedIn
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
B.
resistedOccupationBy
Indicates that one party actively opposed or fought against being occupied or controlled by another party.
-
C.
involvedTown
Indicates that a town participates in, is associated with, or is affected by a particular event, activity, or relationship.
-
D.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
E.
involvedIndependenceMovement
Indicates that an entity actively participated in or contributed to an independence movement seeking political or national self-determination.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
| PDg | Predicate description generation | batch_69fda945e1e08190bf923fcd4d2c548a |
completed | May 8, 2026, 9:13 a.m. |
Created at: May 1, 2026, 2:01 a.m.