Triple
T16615728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natural Community Conservation Planning program |
E403690
|
entity |
| Predicate | typeOfPermit |
P14508
|
FINISHED |
| Object | incidental take permit |
—
|
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: incidental take permit | Statement: [Natural Community Conservation Planning program, typeOfPermit, incidental take permit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPermit Context triple: [Natural Community Conservation Planning program, typeOfPermit, incidental take permit]
-
A.
typeOfLicense
Indicates the specific kind or category of license associated with an entity.
-
B.
trekkingPermitType
Indicates the specific category or kind of permit required or used for undertaking a trekking activity.
-
C.
permitsRequired
Indicates that performing the related action or maintaining the specified relationship is contingent on obtaining one or more formal permits or authorizations.
-
D.
permitType
chosen
Indicates the specific category or kind of permit associated with an entity or activity.
-
E.
environmentalPermit
Indicates that an entity has been granted official authorization to carry out an activity that affects the environment, subject to regulatory conditions.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e375494260819099b6988857c52dde |
completed | April 18, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.