Triple
T30638379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonard Vole |
E779906
|
entity |
| Predicate | hasKeyWitness |
P109136
|
FINISHED |
| Object | Romaine Heilger |
—
|
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: Romaine Heilger | Statement: [Leonard Vole, hasKeyWitness, Romaine Heilger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyWitness Context triple: [Leonard Vole, hasKeyWitness, Romaine Heilger]
-
A.
hasPrimaryWitness
chosen
Indicates that an entity is the main or principal witness associated with another entity or event.
-
B.
hasWitnessType
Indicates that an event, incident, or situation is associated with a specific category or type of witness involved.
-
C.
hasKeyTheorem
Indicates that one entity contains, relies on, or is characterized by a central or foundational theorem associated with the other entity.
-
D.
usesWitnessField
Indicates that an entity performs an action or process that relies on or incorporates a designated witness field as part of its operation or validation.
-
E.
hasKeyAccord
Indicates that one entity possesses or defines the primary key or governing agreement that authorizes or controls another entity.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 29, 2026, 8:29 p.m.