Triple
T10011246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corporal Henderson |
E199377
|
entity |
| Predicate | hasUnspecified |
P30113
|
FINISHED |
| Object | branch of service |
—
|
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: branch of service | Statement: [Corporal Henderson, hasUnspecified, branch of service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnspecified Context triple: [Corporal Henderson, hasUnspecified, branch of service]
-
A.
hasUnknown
chosen
Indicates that an entity possesses or is associated with information, attributes, or values that are not known or not specified.
-
B.
doesNotSpecify
Indicates that the subject intentionally leaves some information, detail, or attribute undefined or unspecified with respect to the object.
-
C.
hasBeenSpeculatedToBe
Indicates that something has been suggested or hypothesized, without firm evidence, to possibly be or correspond to something else.
-
D.
hasSpecification
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
E.
hasUncertainNumber
Indicates that the associated quantity or count is not known precisely or cannot be determined with certainty.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd3b68888190b8a325b52d57c5b8 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:52 p.m.