Triple
T33770072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maretha |
E865353
|
entity |
| Predicate | centralObjectAssociation |
P182347
|
FINISHED |
| Object | the family piano |
—
|
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: the family piano | Statement: [Maretha, centralObjectAssociation, the family piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralObjectAssociation Context triple: [Maretha, centralObjectAssociation, the family piano]
-
A.
centralObjectFunction
Indicates that an object serves as the primary or core element enabling a particular function or set of functions within a system or context.
-
B.
antAssociation
Indicates a relationship in which one entity is associated or interacts in a specific, notable way with ants.
-
C.
centralEntity
Indicates that the subject serves as the primary or most important entity around which related entities, actions, or information are organized.
-
D.
classAssociation
Indicates a relationship where one entity is associated with, but not necessarily a member or subclass of, a particular class or category.
-
E.
rootAssociation
chosen
Indicates a primary or foundational association where one entity serves as the central or originating point for another.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:45 a.m.