Triple
T25272006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morelia spilota |
E633590
|
entity |
| Predicate | isProtectedInSomeRegions |
P158081
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Morelia spilota, isProtectedInSomeRegions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProtectedInSomeRegions Context triple: [Morelia spilota, isProtectedInSomeRegions, true]
-
A.
supportsRegionRestriction
Indicates that an entity enforces or accommodates limitations on availability or access based on geographic regions.
-
B.
suppressedInCountry
Indicates that an entity (such as content, activity, or information) is restricted, censored, or otherwise prevented from being available or expressed within a specified country.
-
C.
isPlayedInRegion
Indicates that an instance of something (such as a game, media, or event) is available to be played or occurs within a specified geographic region.
-
D.
availableInCountry
Indicates that something can be legally or practically obtained, accessed, or used within a specified country.
-
E.
bannedInCountry
Indicates that something is officially prohibited or not allowed within the jurisdiction of a specified country.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba2bb608190bb26a5a496fff3b8 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:16 p.m.