Triple
T32644374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leakee |
E834560
|
entity |
| Predicate | hasRingAttireType |
P185233
|
FINISHED |
| Object | trunks |
—
|
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: trunks | Statement: [Leakee, hasRingAttireType, trunks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRingAttireType Context triple: [Leakee, hasRingAttireType, trunks]
-
A.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
-
B.
hasRingPersonaType
Indicates that an entity’s type or role is defined specifically in the context of its ring-related persona or identity.
-
C.
ringsOn
Indicates that one entity encircles or forms a ring around another entity, typically by being placed around it.
-
D.
hasRingComposition
Indicates that one entity is composed of, or structurally organized around, a ring-like arrangement or circular structure.
-
E.
hasRingRegion
Indicates that one entity possesses or includes a ring-shaped region as part of its structure or spatial extent.
- F. None of above. chosen
Provenance (4 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_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: May 1, 2026, 1:07 a.m.