Triple
T30193743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing Naval Force Channel |
E767565
|
entity |
| Predicate | permanentStatus |
P127
|
FINISHED |
| Object | permanent peacetime force |
—
|
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: permanent peacetime force | Statement: [Standing Naval Force Channel, permanentStatus, permanent peacetime force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentStatus Context triple: [Standing Naval Force Channel, permanentStatus, permanent peacetime force]
-
A.
permanentStatusFrom
Indicates that an entity’s permanent or long-term status is derived from, assigned by, or determined based on another specified source or condition.
-
B.
permanentPosition
Indicates that an entity holds a long-term, ongoing role or job with another entity, without a predefined end date.
-
C.
primaryStatus
Indicates the main or most important status assigned to an entity among potentially multiple statuses.
-
D.
permanentAdoption
Indicates a lasting, legally recognized adoption relationship in which the adoptee becomes a permanent member of the adopter’s family.
-
E.
status
chosen
Indicates the current condition, state, or standing of an entity within a given 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f86218c8190918d9a725306fb43 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:29 p.m.