Triple
T7664310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps traditions |
E173589
|
entity |
| Predicate | reinforce |
P3261
|
FINISHED |
| Object | Marine Corps identity |
—
|
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 identity | Statement: [Marine Corps traditions, reinforce, Marine Corps identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reinforce Context triple: [Marine Corps traditions, reinforce, Marine Corps identity]
-
A.
reinforcedIn
Indicates that one entity is strengthened, supported, or made more robust within, or as a result of conditions in, another entity or context.
-
B.
strengthens
chosen
Indicates that one entity increases the power, effectiveness, or resilience of another.
-
C.
reinforcedPrinciple
Indicates that one entity has strengthened, supported, or validated a principle associated with another entity, making that principle more firmly established or accepted.
-
D.
strengthensFrom
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
-
E.
encourages
Indicates actively motivating, supporting, or giving confidence to another entity to pursue an action, behavior, or state.
- 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.