Triple
T32644372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leakee |
E834560
|
entity |
| Predicate | associatedWithRingStyle |
P88470
|
FINISHED |
| Object | powerhouse |
—
|
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: powerhouse | Statement: [Leakee, associatedWithRingStyle, powerhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRingStyle Context triple: [Leakee, associatedWithRingStyle, powerhouse]
-
A.
associatedWithRing
Indicates that an entity has a connection or relationship with a specific ring, such as ownership, membership, or involvement.
-
B.
usesRingStyle
chosen
Indicates that one entity performs or operates using a particular ring-based style, method, or format.
-
C.
hasRingAttireType
Indicates the type or style of clothing or gear an entity wears specifically for performing or competing in the ring.
-
D.
hasRingComposition
Indicates that one entity is composed of, or structurally organized around, a ring-like arrangement or circular structure.
-
E.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:07 a.m.