Triple
T37463385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcanosaur |
E930974
|
entity |
| Predicate | adaptCount |
P188363
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Volcanosaur, adaptCount, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptCount Context triple: [Volcanosaur, adaptCount, 2]
-
A.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
B.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
C.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
D.
adaptationAs
Indicates that one entity is an adaptation or adapted version of another entity, typically transforming the original into a new form or medium while preserving a core relationship.
-
E.
aimsToAdapt
Indicates that one entity intends to modify or adjust itself, another entity, or a situation in order to better fit certain conditions, requirements, or environments.
- 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_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.