Triple
T16779384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyoko |
E407816
|
entity |
| Predicate | bodyVisibility |
P61724
|
FINISHED |
| Object | synthetic body partly visible |
—
|
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: synthetic body partly visible | Statement: [Kyoko, bodyVisibility, synthetic body partly visible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyVisibility Context triple: [Kyoko, bodyVisibility, synthetic body partly visible]
-
A.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
B.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
viewOfBody
chosen
Indicates a visual representation or perspective that shows the body or a specific part of the body.
-
D.
visibleUnder
Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
-
E.
hasVisibility
Indicates that one entity can perceive, view, or access another entity or its information under certain conditions.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21401b881909bbbc7382e851a90 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.