Triple
T13081608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memphis |
E310219
|
entity |
| Predicate | developmentStartApproximate |
P10779
|
FINISHED |
| Object | mid-1990s |
—
|
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: mid-1990s | Statement: [Memphis, developmentStartApproximate, mid-1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentStartApproximate Context triple: [Memphis, developmentStartApproximate, mid-1990s]
-
A.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
B.
developmentBegan
chosen
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
developmentScale
Indicates the relative size, intensity, or extent to which something is developed or has progressed in its development.
-
D.
developmentIncludes
Indicates that a broader development process or project encompasses or contains a specific component, phase, or activity as part of its overall scope.
-
E.
developmentOpened
Indicates that a development project, phase, or environment has been initiated and made active or accessible.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9811add9881908a92186dab5b6d48 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:01 p.m.