Triple
T27233884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Haddock |
E682224
|
entity |
| Predicate | usesExpression |
P147036
|
FINISHED |
| Object | Blistering barnacles |
—
|
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: Blistering barnacles | Statement: [Captain Haddock, usesExpression, Blistering barnacles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesExpression Context triple: [Captain Haddock, usesExpression, Blistering barnacles]
-
A.
usedInExpression
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
-
B.
usesExpressionSystem
Indicates that one entity employs or relies on a particular expression system (e.g., a biological, genetic, or computational framework) to produce, express, or manipulate another entity.
-
C.
usesTextExpression
chosen
Indicates that one entity employs or represents another entity through a textual expression or string-based form.
-
D.
hasExpression
Indicates that an entity displays or possesses a particular facial or emotional expression.
-
E.
isPartOfExpression
Indicates that something functions as a component or constituent element within a larger expression.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62650ac7081908ebb09374760e877 |
completed | May 2, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:47 a.m.