Triple
T27713618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chin |
E698756
|
entity |
| Predicate | hasAccessRegulationsFor |
P129720
|
FINISHED |
| Object | alpine tundra protection |
—
|
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: alpine tundra protection | Statement: [The Chin, hasAccessRegulationsFor, alpine tundra protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessRegulationsFor Context triple: [The Chin, hasAccessRegulationsFor, alpine tundra protection]
-
A.
hasRegulations
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
B.
hasAccessRegime
chosen
Indicates that one entity is subject to, governed by, or managed under a particular access control regime or set of access rules defined by another entity.
-
C.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
D.
allowsRegulationOf
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
E.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 3:03 p.m.