Triple
T26522298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attention – Tanks! |
E669988
|
entity |
| Predicate | authorRankAtPublication |
P50189
|
FINISHED |
| Object | colonel |
—
|
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: colonel | Statement: [Attention – Tanks!, authorRankAtPublication, colonel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorRankAtPublication Context triple: [Attention – Tanks!, authorRankAtPublication, colonel]
-
A.
authorRank
chosen
Indicates the relative standing or position of an author within a ranked ordering, such as by contribution, importance, or prominence.
-
B.
hasAuthorAffiliationAtTimeOfPublication
Indicates that an author was affiliated with a particular organization or institution at the time a work was published.
-
C.
impactFactorRanking
Indicates the relative position or rank of an entity based on its impact factor compared to others in the same set or category.
-
D.
authorPublished
Indicates that an author has published a particular work (such as a book, article, or paper).
-
E.
hasDBLPAuthorId
Indicates that an entity is associated with a specific author identifier in the DBLP bibliographic database.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 1:28 a.m.