Triple
T5283971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Cross of the Virtuti Militari |
E119567
|
entity |
| Predicate | hasClassRank |
P11443
|
FINISHED |
| Object | Class I |
—
|
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: Class I | Statement: [Grand Cross of the Virtuti Militari, hasClassRank, Class I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassRank Context triple: [Grand Cross of the Virtuti Militari, hasClassRank, Class I]
-
A.
hasRankCategory
chosen
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
B.
hasRankContext
Indicates that an entity’s rank or ordering is defined, interpreted, or constrained within a specific contextual framework or situation.
-
C.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
D.
isRankedAbove
Indicates that one entity holds a higher position or status in an ordered ranking than another entity.
-
E.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.