Triple
T14529395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise Mallard |
E340862
|
entity |
| Predicate | thinksOfFutureAs |
P26266
|
FINISHED |
| Object | years that would belong to her absolutely |
—
|
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: years that would belong to her absolutely | Statement: [Louise Mallard, thinksOfFutureAs, years that would belong to her absolutely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thinksOfFutureAs Context triple: [Louise Mallard, thinksOfFutureAs, years that would belong to her absolutely]
-
A.
futureComponentOf
Indicates that one entity is expected or planned to become a component or part of another entity at some point in the future.
-
B.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
-
C.
hasVisionOf
chosen
Indicates that one entity perceives, imagines, or foresees another entity or scenario, typically in a mental, prophetic, or visualized form.
-
D.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for another entity.
-
E.
futureHeir
Indicates that one entity is designated or expected to inherit from another entity at a future time.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.