Triple
T31462575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Señor de Bizkaia |
E802640
|
entity |
| Predicate | eventuallyHeldBy |
P42393
|
FINISHED |
| Object | Kings of Castile |
—
|
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: Kings of Castile | Statement: [Señor de Bizkaia, eventuallyHeldBy, Kings of Castile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventuallyHeldBy Context triple: [Señor de Bizkaia, eventuallyHeldBy, Kings of Castile]
-
A.
laterHeldBy
chosen
Indicates that an entity was possessed, controlled, or owned by another entity at a subsequent time after an earlier state or holder.
-
B.
hasBeenHeldBy
Indicates that an entity has previously possessed, controlled, or occupied another entity for some duration in the past.
-
C.
hasHeldBy
Indicates that one entity has been physically or conceptually grasped, possessed, or kept in the control of another entity.
-
D.
heldByUntil
Indicates that an entity maintains possession or control of something up to, but not necessarily beyond, a specified time or condition.
-
E.
heldByEnd
Indicates that an object or item is being held or supported specifically at one of its ends by an agent or another object.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 30, 2026, 9:21 p.m.