Triple
T30798862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rumor Mill |
E784309
|
entity |
| Predicate | hasAdaptationStyle |
P64758
|
FINISHED |
| Object | adaptation-focused direction |
—
|
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: adaptation-focused direction | Statement: [The Rumor Mill, hasAdaptationStyle, adaptation-focused direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdaptationStyle Context triple: [The Rumor Mill, hasAdaptationStyle, adaptation-focused direction]
-
A.
hasAdaptationStrategy
Indicates that an entity employs or is associated with a specific method or approach for adapting to changing conditions or requirements.
-
B.
hasAdaptationsIn
Indicates that something possesses or exhibits adaptations within a particular context, environment, or domain.
-
C.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
D.
adaptationStyle
chosen
Indicates how an entity adjusts or modifies its behavior, form, or strategy in response to changing conditions or influences.
-
E.
hasAdaptationRoleIn
Indicates that an entity serves a specific adaptation-related role or function within another entity, process, or context.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:42 p.m.