Triple
T35432523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camerone (Legion commemoration) |
E1024100
|
entity |
| Predicate | coreValueEmphasized |
P17414
|
FINISHED |
| Object | courage |
—
|
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: courage | Statement: [Camerone (Legion commemoration), coreValueEmphasized, courage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreValueEmphasized Context triple: [Camerone (Legion commemoration), coreValueEmphasized, courage]
-
A.
primaryValue
Indicates the main or most significant value associated with an entity, attribute, or measurement within a given context.
-
B.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
C.
designEmphasizes
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
D.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
E.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795b7d77081909bb1be08edf5adef |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.