Triple
T23203680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 66-45 |
E580385
|
entity |
| Predicate | createdRank |
P125294
|
FINISHED |
| Object | General of the Armies |
—
|
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 of the Armies | Statement: [Public Law 66-45, createdRank, General of the Armies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdRank Context triple: [Public Law 66-45, createdRank, General of the Armies]
-
A.
formationRank
Indicates the hierarchical position or level an entity holds within a particular formation or organized group.
-
B.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
C.
inspiredRanks
Indicates that one entity’s example, achievement, or influence motivates another entity to improve or elevate its status, performance, or position.
-
D.
chronRank
Indicates the relative chronological order or ranking of events or time-related entities with respect to one another.
-
E.
changesRankOf
chosen
Indicates a relationship where one entity causes or effects a change in the rank or hierarchical position of 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907b3e88819088a397a99456bf77 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.