Triple
T26458000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedok-class mine countermeasures vessel |
E665545
|
entity |
| Predicate | subRole |
P65943
|
FINISHED |
| Object | mine sweeping |
—
|
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: mine sweeping | Statement: [Bedok-class mine countermeasures vessel, subRole, mine sweeping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subRole Context triple: [Bedok-class mine countermeasures vessel, subRole, mine sweeping]
-
A.
hasSubrole
chosen
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
B.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
C.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
-
D.
specialRole
Indicates that an entity holds a distinctive or exceptional function, status, or responsibility in relation to another entity or context.
-
E.
secretRole
Indicates that an entity holds a role or function that is intentionally hidden or not publicly disclosed 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61291b9588190931535163a538686 |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 12:10 a.m.