Triple
T9592042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USNS |
E231443
|
entity |
| Predicate | notOperatedBy |
P63047
|
FINISHED |
| Object | commissioned warships |
—
|
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: commissioned warships | Statement: [USNS, notOperatedBy, commissioned warships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notOperatedBy Context triple: [USNS, notOperatedBy, commissioned warships]
-
A.
operatedWithout
Indicates that an action, process, or entity functioned or was carried out in the absence of a specified resource, condition, or participant.
-
B.
notManagedBy
chosen
Indicates that an entity is explicitly not under the control, supervision, or administrative responsibility of the specified manager or managing entity.
-
C.
isOperatedIn
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
-
D.
doesNotOperate
Indicates that an entity is not functioning, active, or performing its intended operation in relation to another entity or context.
-
E.
mayBeOperatedBy
Indicates that an entity has the potential or permission to be operated, controlled, or run by 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a10b85881908bfc783dcb7170aa |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.