Triple
T7664309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps traditions |
E173589
|
entity |
| Predicate | embody |
P4755
|
FINISHED |
| Object | Marine Corps ethos |
—
|
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: Marine Corps ethos | Statement: [Marine Corps traditions, embody, Marine Corps ethos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embody Context triple: [Marine Corps traditions, embody, Marine Corps ethos]
-
A.
embodiedBy
chosen
Indicates that an abstract concept, role, or function is physically or concretely realized in a specific entity.
-
B.
supportingBody
Indicates that one entity serves as a supporting or backing body for another entity, providing endorsement, resources, or structural support.
-
C.
eligibleBody
Indicates that an entity qualifies as an appropriate or permitted body (e.g., organization or institution) to participate in or be subject to a specified relationship or action.
-
D.
emulates
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
E.
expresses
Indicates that one entity conveys, communicates, or articulates a thought, feeling, or idea through another medium or form.
- 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.