Triple
T5427186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spacetime Physics |
E121390
|
entity |
| Predicate | hasExerciseType |
P63698
|
FINISHED |
| Object | conceptual problems |
—
|
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: conceptual problems | Statement: [Spacetime Physics, hasExerciseType, conceptual problems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExerciseType Context triple: [Spacetime Physics, hasExerciseType, conceptual problems]
-
A.
hasExerciseFeatures
Indicates that something possesses specific characteristics, attributes, or properties related to exercise or physical activity.
-
B.
hasOrdinaryExercise
Indicates that an entity engages in or is associated with a regular, non-specialized form of physical exercise.
-
C.
participatesInExercise
Indicates that an entity takes part in a physical exercise activity or workout.
-
D.
hasExtraordinaryExercise
Indicates that an entity engages in an unusually intense, prolonged, or otherwise exceptional level of physical exercise beyond typical norms.
-
E.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8910de688190aa0cd80627849a60 |
completed | March 20, 2026, 5:51 p.m. |
Created at: March 20, 2026, 2:06 p.m.