Triple
T20710442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross (United Kingdom) |
E509021
|
entity |
| Predicate | isNonDiscriminatoryByRank |
P141182
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Victoria Cross (United Kingdom), isNonDiscriminatoryByRank, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonDiscriminatoryByRank Context triple: [Victoria Cross (United Kingdom), isNonDiscriminatoryByRank, true]
-
A.
hasComparableRank
Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
-
B.
hasNormativeRank
Indicates that one entity is assigned a particular level, status, or priority within a normative or hierarchical ordering relative to others.
-
C.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
D.
isRank
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
E.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
- F. None of above. chosen
Provenance (4 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1974ba08190b0e5ad529be95e4c |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:14 p.m.