Triple
T24998020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Pickett monument at Gettysburg National Military Park |
E625627
|
entity |
| Predicate | honorsRank |
P51002
|
FINISHED |
| Object | Major 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: Major General | Statement: [George Pickett monument at Gettysburg National Military Park, honorsRank, Major General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsRank Context triple: [George Pickett monument at Gettysburg National Military Park, honorsRank, Major General]
-
A.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
B.
honorsRole
chosen
Indicates that one entity formally recognizes and respects the position, title, or role held by another entity.
-
C.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
D.
honorsNumber
Indicates that one entity formally recognizes or commemorates another by assigning or associating a specific number with it.
-
E.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:04 a.m.