Triple
T7328493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace, Grit, and Glory |
E168935
|
entity |
| Predicate | encapsulatesValue |
P75360
|
FINISHED |
| Object | resilience |
—
|
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: resilience | Statement: [Grace, Grit, and Glory, encapsulatesValue, resilience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encapsulatesValue Context triple: [Grace, Grit, and Glory, encapsulatesValue, resilience]
-
A.
encapsulation
Indicates that one entity encloses, contains, or wraps another entity or set of details within a defined boundary, often hiding internal structure from external access.
-
B.
encapsulatesProtocol
Indicates that one entity implements and contains the functionality of a specific communication or interaction protocol on behalf of another entity.
-
C.
enforcedValue
Indicates that a specific value is imposed or mandated for an entity, leaving no freedom to choose an alternative.
-
D.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
E.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
- F. None of above. chosen
Provenance (4 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a879b88190bef0fb6cbae411ff |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e80ae5688190ac3d6c1bdf9532f0 |
completed | March 27, 2026, 8:26 p.m. |
Created at: March 27, 2026, 3:03 p.m.