Triple
T37460834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class Challenges |
E930911
|
entity |
| Predicate | precedesFeature |
P195954
|
FINISHED |
| Object | later adventure class challenges |
—
|
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: later adventure class challenges | Statement: [Class Challenges, precedesFeature, later adventure class challenges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesFeature Context triple: [Class Challenges, precedesFeature, later adventure class challenges]
-
A.
precedesDisc
Indicates that one discourse segment or unit occurs before another in the sequence of discourse.
-
B.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
-
C.
precedesInStability
Indicates that one entity is more stable than another, coming earlier in an ordering based on stability.
-
D.
usedToPrecede
Indicates that one entity regularly or habitually came before another in time or sequence in the past.
-
E.
precedesInAscent
Indicates that one entity occurs or appears earlier than another in an ordered upward or ascending sequence.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
| PDg | Predicate description generation | batch_69fdf5cfa1ec8190b80d887fa1bfb4cf |
completed | May 8, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:17 p.m.