Triple
T1795741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthropocene |
E39598
|
entity |
| Predicate | hasProposedStart |
P10897
|
FINISHED |
| Object | mid-20th century |
—
|
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-20th century | Statement: [Anthropocene, hasProposedStart, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProposedStart Context triple: [Anthropocene, hasProposedStart, mid-20th century]
-
A.
hasProposedOutcome
Indicates that an action, decision, or process is associated with a suggested or anticipated result that is being put forward but not yet realized or confirmed.
-
B.
hasProposedCause
Indicates that one entity is suggested or hypothesized to be the cause or explanation for another entity or event.
-
C.
hasTimeStart
chosen
Indicates that an event, process, or state begins at a specific point in time.
-
D.
hasProposedResolutionType
Indicates the type or category of resolution that has been formally proposed in relation to an issue, dispute, or decision.
-
E.
hasInitial
Indicates that one entity possesses or is associated with the first letter or starting character of another entity’s name or value.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.