Triple
T149563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intelligence Corps |
E3401
|
entity |
| Predicate | badgeFeature |
P1602
|
FINISHED |
| Object | rose and laurel wreath with crown |
—
|
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: rose and laurel wreath with crown | Statement: [Intelligence Corps, badgeFeature, rose and laurel wreath with crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: badgeFeature Context triple: [Intelligence Corps, badgeFeature, rose and laurel wreath with crown]
-
A.
badge
Indicates that one entity confers, displays, or is associated with a symbolic mark or emblem representing status, achievement, role, or affiliation in relation to another entity.
-
B.
badgeShape
Indicates the geometric form or outline that a badge takes.
-
C.
badgeReverseDesign
Indicates the design or imagery that appears on the reverse (back) side of a badge.
-
D.
qualificationBadge
Indicates that an entity has been awarded or holds a specific qualification badge signifying a certified skill, status, or achievement.
-
E.
badgeObverseDesign
chosen
Indicates the design or imagery that appears on the front (obverse) side of a badge.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.