Triple
T82079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congressional Gold Medal |
E1648
|
entity |
| Predicate | typicalRecipient |
P485
|
FINISHED |
| Object | civilians |
—
|
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: civilians | Statement: [Congressional Gold Medal, typicalRecipient, civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRecipient Context triple: [Congressional Gold Medal, typicalRecipient, civilians]
-
A.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
B.
coRecipientWith
Indicates that two or more entities receive the same item, benefit, or communication together as joint recipients.
-
C.
scopeOfRecipients
chosen
Indicates the range or group of recipients to whom something (such as information, communication, or benefits) is directed or applicable.
-
D.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
-
E.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a25053ca208190a371b0d38000c2b9 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb2998c819082681da74601d446 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.