Triple
T33036788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landgrave of Hesse-Philippsthal-Barchfeld |
E845335
|
entity |
| Predicate | rankComparedToDuke |
P22893
|
FINISHED |
| Object | lower |
—
|
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: lower | Statement: [Landgrave of Hesse-Philippsthal-Barchfeld, rankComparedToDuke, lower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankComparedToDuke Context triple: [Landgrave of Hesse-Philippsthal-Barchfeld, rankComparedToDuke, lower]
-
A.
recognizedAsDuke
Indicates that an entity is formally acknowledged or accepted as holding the title or status of a duke.
-
B.
rankComparedTo
chosen
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
C.
comparativeRankInUS
Indicates the relative ranking or position of an entity within the United States compared to other entities of the same type.
-
D.
notableDuke
Indicates that a person holds or held the title of duke and is distinguished or prominent in some notable way.
-
E.
classRank
Indicates the relative academic standing or position of an entity within a class or cohort based on performance or criteria.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:24 a.m.