Triple
T32509002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Druig |
E830877
|
entity |
| Predicate | establishesCommunityIn |
P26923
|
FINISHED |
| Object | Amazon rainforest |
—
|
NE NERFINISHED |
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: Amazon rainforest | Statement: [Druig, establishesCommunityIn, Amazon rainforest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesCommunityIn Context triple: [Druig, establishesCommunityIn, Amazon rainforest]
-
A.
foundedCommunity
Indicates that an entity established or created a community, organization, or group.
-
B.
formsCommunityIn
chosen
Indicates that an entity comes together with others to establish or participate in a community within a particular context or location.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
formsBiStateCommunityWith
Indicates that two entities jointly constitute or participate in a shared bi-state community spanning both of their jurisdictions.
-
E.
connectsCommunity
Indicates a relationship where an entity links or brings together members or groups within a community, fostering interaction or cohesion among them.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1 a.m.