Triple
T37193498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodoc Mountains protected area |
E921526
|
entity |
| Predicate | hasAllowedUse |
P196846
|
FINISHED |
| Object | scientific research |
—
|
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: scientific research | Statement: [Bodoc Mountains protected area, hasAllowedUse, scientific research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllowedUse Context triple: [Bodoc Mountains protected area, hasAllowedUse, scientific research]
-
A.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
isStillAllowedFor
Indicates that one entity continues to have permission or authorization to access, use, or perform something in relation to another entity.
-
D.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
E.
hasPermit
Indicates that an entity possesses an official authorization or license granting it permission to perform a specific activity or hold a certain status.
- F. None of above. chosen
Provenance (4 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: May 3, 2026, 4:15 p.m.