Triple
T21777949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhonghua Minguo guoge |
E537629
|
entity |
| Predicate | respectGesture |
P16866
|
FINISHED |
| Object | standing at attention |
—
|
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: standing at attention | Statement: [Zhonghua Minguo guoge, respectGesture, standing at attention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: respectGesture Context triple: [Zhonghua Minguo guoge, respectGesture, standing at attention]
-
A.
signatureGesture
Indicates a distinctive or characteristic gesture that is uniquely associated with a particular individual or entity.
-
B.
gesture
chosen
Indicates that an entity uses a bodily movement or sign to communicate or express something to another entity.
-
C.
regards
Indicates that one entity considers, views, or treats another entity in a particular way or with a certain attitude.
-
D.
honour
Indicates showing respect, admiration, or recognition toward someone or something, often through actions, words, or ceremonial acknowledgment.
-
E.
aspect
Indicates a specific temporal phase or manner in which an action, event, or state unfolds or is viewed (e.g., ongoing, completed, habitual).
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0462b094c81908207073c278a58fe |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.