Triple
T36489291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuroplasticity |
E899011
|
entity |
| Predicate | occursAcross |
P186437
|
FINISHED |
| Object | Lifespan |
—
|
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: Lifespan | Statement: [Neuroplasticity, occursAcross, Lifespan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursAcross Context triple: [Neuroplasticity, occursAcross, Lifespan]
-
A.
usedAcross
Indicates that something is utilized or applied in multiple different contexts, locations, or domains.
-
B.
appliesAcross
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
-
C.
occursTo
Indicates that an event, idea, or realization happens in or comes to the mind or awareness of an entity.
-
D.
occursFor
Indicates that an event, process, or condition takes place in relation to, or on behalf of, a particular entity or context.
-
E.
occursInEvery
Indicates that the related event, state, or condition takes place within each instance of the specified context or domain, without exception.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:10 p.m.