Triple
T37241726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Efe people |
E923727
|
entity |
| Predicate | contemporaryChallenges |
P71878
|
FINISHED |
| Object | deforestation |
—
|
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: deforestation | Statement: [Efe people, contemporaryChallenges, deforestation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryChallenges Context triple: [Efe people, contemporaryChallenges, deforestation]
-
A.
currentChallenges
chosen
Indicates the difficulties or obstacles an entity is presently facing or dealing with.
-
B.
contemporaryChange
Indicates a change or transformation that occurs during the same time period as another referenced event or state.
-
C.
notableModernIssue
Indicates that the subject is recognized as a significant or widely discussed issue in contemporary times.
-
D.
contemporaryProcess
Indicates that one process occurs in the same time period as, or overlaps temporally with, another process.
-
E.
contemporaryEvents
Indicates that two or more events occur in the same time period or overlap temporally.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.