Triple
T31957750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S48 |
E815952
|
entity |
| Predicate | associatedWithServiceStatus |
P206134
|
FINISHED |
| Object | commissioned warship |
—
|
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 warship | Statement: [S48, associatedWithServiceStatus, commissioned warship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithServiceStatus Context triple: [S48, associatedWithServiceStatus, commissioned warship]
-
A.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
B.
linkedByServiceTo
Indicates that one entity is connected or associated with another through a specific service acting as the linking mechanism.
-
C.
associationStatus
Indicates the current state or condition of an established association or relationship between entities.
-
D.
associatedWithProvider
Indicates that one entity has a connection or relationship with a specific provider, such as being supplied, managed, or serviced by that provider.
-
E.
typicalServiceStatus
Indicates the usual or standard operational state or condition that a service is expected to be in under normal circumstances.
- F. None of above. chosen
Provenance (4 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:08 a.m.