Triple
T7664251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps ceremonies |
E173588
|
entity |
| Predicate | coreValuesReinforced |
P50891
|
FINISHED |
| Object | honor |
—
|
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: honor | Statement: [Marine Corps ceremonies, coreValuesReinforced, honor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreValuesReinforced Context triple: [Marine Corps ceremonies, coreValuesReinforced, honor]
-
A.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
B.
coreCommitment
Indicates a fundamental, central obligation or promise that defines the primary responsibility or dedication within a relationship or agreement.
-
C.
associatedWithBrandValues
Indicates that one entity is connected or aligned with the brand values, principles, or identity represented by another entity.
-
D.
reinforcedPrinciple
chosen
Indicates that one entity has strengthened, supported, or validated a principle associated with another entity, making that principle more firmly established or accepted.
-
E.
vowedVirtue
Indicates that an entity has formally promised or committed to uphold a particular virtue or moral quality.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.