Triple
T11828770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hook and Cod wars |
E281326
|
entity |
| Predicate | involvedClass |
P1256
|
FINISHED |
| Object | nobility of Holland |
—
|
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: nobility of Holland | Statement: [Hook and Cod wars, involvedClass, nobility of Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedClass Context triple: [Hook and Cod wars, involvedClass, nobility of Holland]
-
A.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
-
B.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
C.
involvedBranch
Indicates that a particular branch (such as a location, division, or sub-unit) participates in, is associated with, or plays a role in the referenced event, process, or relationship.
-
D.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
E.
mayBeInvolvedIn
Indicates that an entity has a possible, but not certain, participation or role in a particular event, activity, or situation.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62b75dc8190b27d24e46a262a11 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.