Triple
T17141165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelly Chan |
E415964
|
entity |
| Predicate | positionInScene |
P83026
|
FINISHED |
| Object | leading figure |
—
|
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: leading figure | Statement: [Kelly Chan, positionInScene, leading figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInScene Context triple: [Kelly Chan, positionInScene, leading figure]
-
A.
positionInFrame
Indicates the spatial location or coordinates of an entity within a specific frame or reference image.
-
B.
positionInHierarchy
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
C.
positionOnPhysics
Indicates a stance, viewpoint, or opinion that one entity holds regarding the subject or field of physics.
-
D.
positionInField
chosen
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
E.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d44a508190a3a149c3a64957f5 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.