Triple
T17910281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapis Lazuli |
E447801
|
entity |
| Predicate | relationshipWithJasper |
P2830
|
FINISHED |
| Object | abusive |
—
|
LITERAL 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: abusive | Statement: [Lapis Lazuli, relationshipWithJasper, abusive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithJasper Context triple: [Lapis Lazuli, relationshipWithJasper, abusive]
-
A.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
reportsSymbolicallyTo
Indicates that one entity formally reports to another through symbolic, representational, or non-literal means rather than through direct, operational authority.
-
C.
partnerStudio
Indicates that one entity serves as a partner studio associated with, collaborating with, or officially linked to another entity.
-
D.
reportsFor
Indicates that one entity is subordinate to another and is required to provide updates or answer to that entity, typically within an organizational or hierarchical structure.
-
E.
partnerInOrganizationWith
Indicates that two entities are associated as partners within the same organization or organizational context.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49ea017d081908be850a39edf601f |
completed | April 19, 2026, 9:21 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.