Triple
T19808596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knight of the Order of Prince Henry |
E475880
|
entity |
| Predicate | hasRankInPortuguese |
P133169
|
FINISHED |
| Object | Cavaleiro |
—
|
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: Cavaleiro | Statement: [Knight of the Order of Prince Henry, hasRankInPortuguese, Cavaleiro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankInPortuguese Context triple: [Knight of the Order of Prince Henry, hasRankInPortuguese, Cavaleiro]
-
A.
rankInPortugal
chosen
Indicates the position or standing that something holds within a ranking specific to Portugal.
-
B.
equivalentRankInPortugueseAirForce
Indicates that two military ranks are considered equivalent within the rank structure of the Portuguese Air Force.
-
C.
equivalentRankInPortugueseArmy
Indicates that two military ranks are considered equivalent within the rank structure of the Portuguese Army.
-
D.
equivalentRankInPortugueseNavy
Indicates that two military ranks are considered equivalent in status or hierarchy within the Portuguese Navy.
-
E.
isLusophoneSurname
Indicates that a surname belongs to or is commonly used in Portuguese-speaking (Lusophone) cultures.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65429fec8819091e20908101b50eb |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.