Triple
T13268225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GOC-in-C Second Army |
E315979
|
entity |
| Predicate | notableHolderRank |
P61801
|
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: [GOC-in-C Second Army, notableHolderRank, General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHolderRank Context triple: [GOC-in-C Second Army, notableHolderRank, General]
-
A.
notableRank
chosen
Indicates that an entity holds a distinguished or significant position or level within a ranking or hierarchy.
-
B.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
C.
notableHolderRole
Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
-
D.
lastHolderRank
Indicates the rank or position held by the most recent entity that possessed or held a given item, title, or role.
-
E.
titleHolderRank
Indicates the relative position or level of precedence assigned to a title holder within a ranked order or hierarchy.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.