Triple
T6981859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shompen people |
E161864
|
entity |
| Predicate | protectionPolicy |
P73638
|
FINISHED |
| Object | restricted area regulations |
—
|
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: restricted area regulations | Statement: [Shompen people, protectionPolicy, restricted area regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectionPolicy Context triple: [Shompen people, protectionPolicy, restricted area regulations]
-
A.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
B.
protectionLevel
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
C.
protectionCategory
Indicates a classification relationship where an entity is assigned to a specific type or level of protection based on defined protective criteria or rules.
-
D.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6d3f3c8190b0121f7934440c34 |
completed | March 27, 2026, 7:33 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8e2d7b48190b37bb13984663cde |
completed | March 27, 2026, 7:22 p.m. |
Created at: March 27, 2026, 2:31 p.m.