Triple
T28154493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austro-Hungarian Army ranks |
E714704
|
entity |
| Predicate | NCOrank |
P164075
|
FINISHED |
| Object | Feldwebel |
—
|
NE NERFINISHED |
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: Feldwebel | Statement: [Austro-Hungarian Army ranks, NCOrank, Feldwebel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NCOrank Context triple: [Austro-Hungarian Army ranks, NCOrank, Feldwebel]
-
A.
NCOrank
chosen
Indicates a hierarchical ranking relationship between entities within the context of a non-commissioned officer (NCO) rank structure.
-
B.
rankInNorthCarolinaByPopulation
Indicates the position an entity holds in an ordered list of North Carolina entities when sorted by their population size.
-
C.
GreeneRank
Indicates a ranking or ordered position assigned according to Greene’s specific criteria or system.
-
D.
regionOfNorthCarolina
Indicates that a location or entity is situated within the geographic boundaries of North Carolina.
-
E.
countyRank
Indicates the relative position or standing of a county within a larger ordered set, typically based on some quantitative measure such as size, population, or performance.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 10:01 p.m.