Triple
T4574338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Armed Forces (ceremonial) |
E123106
|
entity |
| Predicate | followsProtocol |
P9964
|
FINISHED |
| Object | Singapore military ceremonial protocol |
—
|
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: Singapore military ceremonial protocol | Statement: [Singapore Armed Forces (ceremonial), followsProtocol, Singapore military ceremonial protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsProtocol Context triple: [Singapore Armed Forces (ceremonial), followsProtocol, Singapore military ceremonial protocol]
-
A.
hasProtocol
chosen
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
B.
supportedProtocol
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
C.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
D.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
E.
specifiesProtocol
Indicates that one entity defines or designates the communication or interaction protocol to be used 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c9f0bc81908d87f01ab067818a |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.