Triple
T33317702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Services |
E853056
|
entity |
| Predicate | includesBranchType |
P1988
|
FINISHED |
| Object | naval service |
—
|
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: naval service | Statement: [Sea Services, includesBranchType, naval service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBranchType Context triple: [Sea Services, includesBranchType, naval service]
-
A.
branchType
chosen
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
-
B.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger branch.
-
C.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
D.
hasBranchName
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
-
E.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a030425fa1c81908748583513552d2b |
completed | May 12, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0303ced28081908588b8a14c23efe9 |
completed | May 12, 2026, 10:41 a.m. |
Created at: May 1, 2026, 1:33 a.m.