Triple
T33826002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | From the Other Side |
E866956
|
entity |
| Predicate | recurringFeatureOf |
P69479
|
FINISHED |
| Object | Hopscotch |
—
|
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: Hopscotch | Statement: [From the Other Side, recurringFeatureOf, Hopscotch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringFeatureOf Context triple: [From the Other Side, recurringFeatureOf, Hopscotch]
-
A.
featuresRecurringElement
chosen
Indicates that something includes an element, motif, or component that appears repeatedly over time or across multiple instances.
-
B.
recurringActivity
Indicates that an activity or event occurs repeatedly over time according to some regular or defined pattern.
-
C.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
D.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
E.
recurringIssue
Indicates that a problem or issue reappears or persists over time, occurring repeatedly rather than being a one-time event.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7001c04d881909f2541fab62d8b19 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.