Triple
T32729488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic Naval Squadron |
E836908
|
entity |
| Predicate | memberStateRole |
P139763
|
FINISHED |
| Object | contributes ships |
—
|
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: contributes ships | Statement: [Baltic Naval Squadron, memberStateRole, contributes ships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberStateRole Context triple: [Baltic Naval Squadron, memberStateRole, contributes ships]
-
A.
memberStateSide1
Indicates that an entity participates as the first member state (or party) on one side of a bilateral or multilateral relationship or agreement.
-
B.
memberStatesAreMemberOf
Indicates that certain states belong to or hold membership in a particular organization, group, or union.
-
C.
knownMemberRole
Indicates that an entity is recognized as holding a specific role or position within a group, organization, or membership context.
-
D.
memberStateIntended
Indicates that a particular state is designated or intended to be a member of a specified organization, agreement, or grouping.
-
E.
memberRole_3
chosen
Indicates that an entity holds a specific role or position as a member within a group, organization, or context.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:11 a.m.