Triple
T36654651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sméagol |
E904955
|
entity |
| Predicate | motionCapturePioneer |
P186125
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sméagol, motionCapturePioneer, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motionCapturePioneer Context triple: [Sméagol, motionCapturePioneer, yes]
-
A.
motionCapturePerformer
Indicates a relationship where a performer provides motion data, typically through sensors or tracking, to drive the movement of a digital character or animation.
-
B.
protagonistMotionCapture
Indicates that motion capture data is being recorded or applied specifically to the story’s protagonist character.
-
C.
modelsMotionOf
Indicates that one entity provides a representation or simulation of the motion or movement behavior of another entity.
-
D.
movementFeatured
Indicates that a particular movement, action, or motion is prominently highlighted or given special emphasis within a broader context or sequence.
-
E.
odiCapNumber
Indicates the unique sequential cap number assigned to a player for their debut in One Day International (ODI) cricket.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.