Triple
T24200074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General John Stark Day |
E599949
|
entity |
| Predicate | honoreeMilitaryRank |
P52914
|
FINISHED |
| Object | general |
—
|
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: general | Statement: [General John Stark Day, honoreeMilitaryRank, general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoreeMilitaryRank Context triple: [General John Stark Day, honoreeMilitaryRank, general]
-
A.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
B.
isMilitaryRank
chosen
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
C.
producedMilitaryRank
Indicates that one entity is responsible for conferring, generating, or resulting in the military rank held by another entity.
-
D.
namedForMilitaryRank
Indicates that one entity is named after or in honor of a specific military rank held by a person or associated with a military position.
-
E.
militaryRankBeforeAccession
Indicates the military rank held by an individual prior to their accession to a particular office, position, or status.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca08874819081dd6613ac462c40 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.