Triple
T29512518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Hilaire/Lange National Park |
E748693
|
entity |
| Predicate | allowsUseType |
P7913
|
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: [Saint-Hilaire/Lange National Park, allowsUseType, scientific research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsUseType Context triple: [Saint-Hilaire/Lange National Park, allowsUseType, scientific research]
-
A.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
B.
eligibleUses
chosen
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
C.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
D.
allowsCartUse
Indicates that one entity permits another entity to use or access a cart for its intended purpose.
-
E.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 4:33 p.m.