Triple
T34926091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Riker |
E1007287
|
entity |
| Predicate | sharesPersonalityTraitsWith |
P112715
|
FINISHED |
| Object | William T. Riker |
—
|
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: William T. Riker | Statement: [Thomas Riker, sharesPersonalityTraitsWith, William T. Riker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPersonalityTraitsWith Context triple: [Thomas Riker, sharesPersonalityTraitsWith, William T. Riker]
-
A.
sharesCharacterWith
Indicates that two entities have at least one character (such as a letter, symbol, or glyph) in common.
-
B.
sharesAppearanceTraitWith
Indicates that two entities possess at least one similar or matching visual or appearance-related characteristic.
-
C.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
D.
associatedWithPersonaTrait
chosen
Indicates that an entity is linked to or characterized by a particular persona trait or attribute.
-
E.
sharesFateWith
Indicates that two or more entities are bound to experience the same outcome, destiny, or consequences.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4 p.m.