Triple
T6360756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Nature Reserve |
E143100
|
entity |
| Predicate | isOftenManagedBy |
P70201
|
FINISHED |
| Object | national conservation agency |
—
|
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: national conservation agency | Statement: [National Nature Reserve, isOftenManagedBy, national conservation agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenManagedBy Context triple: [National Nature Reserve, isOftenManagedBy, national conservation agency]
-
A.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
B.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
-
C.
notManagedBy
Indicates that an entity is explicitly not under the control, supervision, or administrative responsibility of the specified manager or managing entity.
-
D.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
E.
nearbyManagedBy
Indicates that one entity is located close to another entity that has management or administrative responsibility over it.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067fa0d0c819098d01545849142fc |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:32 p.m.