Triple
T38590987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hrothgar |
E932451
|
entity |
| Predicate | sharesReleaseWithRace |
P202944
|
FINISHED |
| Object | Viera |
—
|
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: Viera | Statement: [Hrothgar, sharesReleaseWithRace, Viera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesReleaseWithRace Context triple: [Hrothgar, sharesReleaseWithRace, Viera]
-
A.
sharesTimeWith
Indicates that two entities are present or active during overlapping or the same time period.
-
B.
sharesRecordWith
Indicates that two entities have at least one record or data entry in common, or are both associated with the same record.
-
C.
sharesRuleWith
Indicates that two or more entities are governed by, comply with, or are associated with the same rule or set of rules.
-
D.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
E.
sharesControlWith
Indicates that control, authority, or decision-making power over something is jointly held or exercised between the related entities.
- F. None of above. chosen
Provenance (4 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00d24043e8819090cc473b6c0923d0 |
completed | May 10, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_6a00d1ec12fc81908c514ed088ef8300 |
completed | May 10, 2026, 6:43 p.m. |
| PDg | Predicate description generation | batch_6a00d23f402c8190bf49c0d4cce10b73 |
completed | May 10, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:32 p.m.