Triple
T37632617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perfect Plex (as tribute) |
E936392
|
entity |
| Predicate | basedOnMove |
P200041
|
FINISHED |
| Object | Perfect Plex |
—
|
NE NERFINISHED |
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: Perfect Plex | Statement: [Perfect Plex (as tribute), basedOnMove, Perfect Plex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnMove Context triple: [Perfect Plex (as tribute), basedOnMove, Perfect Plex]
-
A.
basedOnMovement
Indicates that something is determined, derived, or decided according to the movement or motion of an entity.
-
B.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
C.
basedOnStrategyOf
Indicates that one entity’s strategy is derived from, influenced by, or constructed using the strategy of another entity.
-
D.
previouslyBasedOn
Indicates that something was formerly derived from, adapted from, or dependent on another source, but is no longer based on it in its current state.
-
E.
basedOnPlayBy
Indicates that something (typically a creative work) is derived or adapted from a play authored by a specified entity.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69ff6c04fa208190b1fab40a71ef923f |
completed | May 9, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.