Triple
T33633441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | armed forces of the North German Confederation |
E861626
|
entity |
| Predicate | secondaryBranch |
P198398
|
FINISHED |
| Object | navy |
—
|
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: navy | Statement: [armed forces of the North German Confederation, secondaryBranch, navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBranch Context triple: [armed forces of the North German Confederation, secondaryBranch, navy]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
secondaryBranchColor
Indicates the color assigned to a secondary or subordinate branch in relation to a primary branch.
-
C.
secondaryHub
Indicates that an entity functions as a secondary or backup hub in relation to a primary hub within a network or system.
-
D.
secondaryLine
Indicates that something serves as a secondary or auxiliary line in relation to a primary or main line.
-
E.
secondarySingle
Indicates that an entity serves as a secondary, but singular, counterpart or role in relation to another primary entity.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
| PDg | Predicate description generation | batch_69fee0b03a0c81909117dc5915d77295 |
completed | May 9, 2026, 7:22 a.m. |
Created at: May 1, 2026, 1:41 a.m.