Triple
T16829799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helder Expedition |
E409117
|
entity |
| Predicate | outcomeDescribedAs |
P22390
|
FINISHED |
| Object | inconclusive tactically |
—
|
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: inconclusive tactically | Statement: [Helder Expedition, outcomeDescribedAs, inconclusive tactically]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeDescribedAs Context triple: [Helder Expedition, outcomeDescribedAs, inconclusive tactically]
-
A.
describesOutcomeOf
chosen
Indicates that one entity specifies or characterizes the result, consequence, or outcome produced by another entity or process.
-
B.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
outcomeSummary
Indicates a concise description or overview of the result or consequences of an action, event, or process.
-
E.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b316acc881909c686add53d72388 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.