Triple
T27811282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snap Wexley |
E702523
|
entity |
| Predicate | hasDroidCompanion |
P83932
|
FINISHED |
| Object | Mister Bones |
—
|
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: Mister Bones | Statement: [Snap Wexley, hasDroidCompanion, Mister Bones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDroidCompanion Context triple: [Snap Wexley, hasDroidCompanion, Mister Bones]
-
A.
supportsCompanion
Indicates that one entity provides assistance, encouragement, or backing to another entity in a companion or partner role.
-
B.
hasCompanionPlatform
Indicates that an entity is associated with or supported by an additional platform that accompanies or complements it.
-
C.
hasAndroidPartner
Indicates that an entity has another entity as its romantic or life partner who is an android.
-
D.
hasAndroid
Indicates that an entity possesses, is equipped with, or is associated with an Android device, system, or component.
-
E.
hasDroidCharacter
chosen
Indicates that an entity features or includes a character that is a droid.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:42 p.m.