Triple
T37923669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archduchess Harriet / Archduke Harry |
E946032
|
entity |
| Predicate | isPursuerOf |
P57748
|
FINISHED |
| Object | Orlando |
—
|
NE NERFINISHED |
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: Orlando | Statement: [Archduchess Harriet / Archduke Harry, isPursuerOf, Orlando]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPursuerOf Context triple: [Archduchess Harriet / Archduke Harry, isPursuerOf, Orlando]
-
A.
pursuerDescription
Indicates that one entity is actively chasing, following, or seeking to catch another entity.
-
B.
claimedToPursue
Indicates that an entity has stated or asserted an intention to pursue another entity, goal, or course of action.
-
C.
partialPursuer
Indicates that one entity is attempting to pursue or chase another, but only to a limited, incomplete, or non-exclusive extent.
-
D.
chases
Indicates that one entity actively pursues another, typically moving after it in an attempt to catch or reach it.
-
E.
pursuingCharacter
chosen
Indicates that one character is actively chasing, seeking, or attempting to catch or reach another character.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.