Triple
T7551087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage buffer boundary |
E178534
|
entity |
| Predicate | canRestrict |
P47306
|
FINISHED |
| Object | construction activities |
—
|
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: construction activities | Statement: [UNESCO World Heritage buffer boundary, canRestrict, construction activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRestrict Context triple: [UNESCO World Heritage buffer boundary, canRestrict, construction activities]
-
A.
mayRestrictActivity
chosen
Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
-
B.
canEnforce
Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon another entity.
-
C.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
canBlock
Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect of another entity.
-
E.
canOwn
Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b50e5c8190817c1e968294d1ad |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.