Triple
T3505529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marchioness |
E74065
|
entity |
| Predicate | rankRelativeToKnight |
P22893
|
FINISHED |
| Object | above knight |
—
|
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: above knight | Statement: [Marchioness, rankRelativeToKnight, above knight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankRelativeToKnight Context triple: [Marchioness, rankRelativeToKnight, above knight]
-
A.
laterNumberOfKnights
Indicates that one entity has a greater (later or higher) number of knights than another entity in a comparative context.
-
B.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
C.
rankComparedTo
chosen
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
-
D.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
E.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf38e988190998d722b95830411 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.