Triple
T19024137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajloun Forest Reserve |
E465563
|
entity |
| Predicate | supportsLocalCommunities |
P11337
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ajloun Forest Reserve, supportsLocalCommunities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLocalCommunities Context triple: [Ajloun Forest Reserve, supportsLocalCommunities, yes]
-
A.
hasLocalCommunities
Indicates that an entity is associated with or contains smaller, localized community groups within a specific area or region.
-
B.
supportsCommunity
chosen
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
C.
hasRemoteCommunities
Indicates that an entity maintains or is associated with communities located in distant or geographically isolated areas.
-
D.
supportsCommunityContent
Indicates that an entity enables, hosts, or facilitates content created and shared by its user or community base.
-
E.
hasLocalGovernmentCommunity
Indicates that one entity possesses or is associated with a community-level local government authority responsible for administering that area.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6e166088190937ef19739437f7c |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.