Triple
T37460560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad Scientist |
E930905
|
entity |
| Predicate | expansionAdventureType |
P190722
|
FINISHED |
| Object | Adventure |
—
|
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: Adventure | Statement: [Mad Scientist, expansionAdventureType, Adventure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionAdventureType Context triple: [Mad Scientist, expansionAdventureType, Adventure]
-
A.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
B.
expansionPack
Indicates that one item serves as an add-on or supplementary content package that extends the features or scope of another item.
-
C.
settingOfAdventure
Indicates that a location or environment serves as the primary setting where an adventure takes place.
-
D.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
E.
ADVENDOExpansion
Indicates an expansion-related relationship, where something grows, extends, or increases in scope, size, or influence relative to another entity or context.
- 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_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.