Triple
T14444874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Meares |
E358177
|
entity |
| Predicate | allegedToHaveRaised |
P52031
|
FINISHED |
| Object | British flag at Nootka Sound |
—
|
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: British flag at Nootka Sound | Statement: [John Meares, allegedToHaveRaised, British flag at Nootka Sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedToHaveRaised Context triple: [John Meares, allegedToHaveRaised, British flag at Nootka Sound]
-
A.
raisedWith
Indicates that two or more entities grew up together in the same household or close environment during their formative years.
-
B.
raisedTo
Indicates that one entity has been elevated, lifted, or brought up to a higher level, position, or state by another entity.
-
C.
raisedOn
Indicates that an entity was nurtured, brought up, or spent its formative period in a particular place, environment, or context.
-
D.
raisedAt
Indicates that something was brought up, mentioned, or initiated at a particular time, place, or contextual point.
-
E.
allegedAction
chosen
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915e76f481909fe9462f964b5b1c |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.