Triple
T27857174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Albion (support role) |
E704119
|
entity |
| Predicate | supportedByBranch |
P68040
|
FINISHED |
| Object | Imperial German Navy |
—
|
NE NERFINISHED |
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: Imperial German Navy | Statement: [Operation Albion (support role), supportedByBranch, Imperial German Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedByBranch Context triple: [Operation Albion (support role), supportedByBranch, Imperial German Navy]
-
A.
supportingBranch
chosen
Indicates that one branch structurally or functionally supports another branch.
-
B.
defaultBranchSupport
Indicates that an entity provides or has support for a designated default branch within a branching or version-control structure.
-
C.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
usedByBranch
Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
-
E.
supportedFrom
Indicates that one entity provides backing, assistance, or justification for another entity, often serving as the source or basis of that support.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a001cc0ff588190bb7c8a6fd427d02b |
completed | May 10, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_6a001b3ea18c8190aeda7a32b2697490 |
completed | May 10, 2026, 5:44 a.m. |
Created at: April 27, 2026, 6:15 p.m.