Triple
T8431417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Reacher |
E199122
|
entity |
| Predicate | dischargeStatus |
P83316
|
FINISHED |
| Object | honorably discharged |
—
|
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: honorably discharged | Statement: [Jack Reacher, dischargeStatus, honorably discharged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dischargeStatus Context triple: [Jack Reacher, dischargeStatus, honorably discharged]
-
A.
dischargeType
Indicates the manner or category of how something is released, emitted, or discharged from a source.
-
B.
hasDischarge
Indicates that one entity releases, emits, or expels a substance, energy, or flow from itself.
-
C.
dischargeRank
Indicates the rank or status an individual held at the time they were discharged from a role, service, or organization.
-
D.
dischargesFrom
Indicates that something (such as a fluid, substance, or energy) flows or is released out of a specified source or origin.
-
E.
dischargeLocation
Indicates the place or facility where an entity (such as a person, object, or substance) is released, sent, or discharged to after a prior state or process.
- 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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:07 p.m.