Triple
T27349782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maarva Andor |
E684322
|
entity |
| Predicate | associatedDroid |
P113623
|
FINISHED |
| Object | B2EMO |
—
|
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: B2EMO | Statement: [Maarva Andor, associatedDroid, B2EMO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDroid Context triple: [Maarva Andor, associatedDroid, B2EMO]
-
A.
associatedMob
Indicates a relationship where one entity is linked or connected to a particular mob (mobile entity), typically as its counterpart, partner, or related unit.
-
B.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
C.
relatedToDevice
chosen
Indicates that there exists a general association or connection between an entity and a device, without specifying the exact nature of that relationship.
-
D.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
E.
associatedItem
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: April 27, 2026, 11:47 a.m.