Triple
T36720331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trina Gavin |
E907039
|
entity |
| Predicate | relatedWorkFeature |
P205021
|
FINISHED |
| Object | Jade |
unclear NED1
|
NE FINISHED |
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: Jade | Statement: [Trina Gavin, relatedWorkFeature, Jade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkFeature Context triple: [Trina Gavin, relatedWorkFeature, Jade]
-
A.
relatedWorkByKey
Indicates a relationship where one work is linked or associated to another work identified by a specific key or identifier.
-
B.
relatedWorkForm
Indicates a relationship in which one work is connected to another through a different form or version (e.g., adaptation, translation, or other format variation).
-
C.
relatedWorkBySubject
Indicates a relationship where one work is connected to another through sharing the same subject or topic.
-
D.
relatedWorkByAttribution
Indicates that one work is connected to another through explicit attribution, such as citation, acknowledgment, or credit given by the creator or source.
-
E.
relatedWorkByDedicatee
Indicates that a work is related to another work through the person to whom it is dedicated (the dedicatee).
- F. None of above. chosen
Provenance (5 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3c1727dbec8190bbc7ca0bc96e3897 |
completed | June 24, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.