Triple
T11666459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mame Dennis |
E277261
|
entity |
| Predicate | inUniverseLifestyle |
P97831
|
FINISHED |
| Object | extravagant |
—
|
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: extravagant | Statement: [Mame Dennis, inUniverseLifestyle, extravagant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseLifestyle Context triple: [Mame Dennis, inUniverseLifestyle, extravagant]
-
A.
lifestyle
Indicates that an entity’s way of living or habitual behaviors are associated with, influence, or characterize another entity or outcome.
-
B.
lifestyleFeature
chosen
Indicates that one entity offers, includes, or is characterized by a particular lifestyle-related amenity, attribute, or quality for another entity.
-
C.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
D.
universeActivity
Indicates an activity, process, or event that occurs at the scale of, or throughout, the universe.
-
E.
lifeHabit
Indicates the typical way an organism lives or behaves in its environment, such as its mode of life, activity pattern, or ecological lifestyle.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a43f438081909da476294a057c38 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.