Triple
T149245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts of Parliament |
E3395
|
entity |
| Predicate | maySpecify |
P2150
|
FINISHED |
| Object | territorial extent |
—
|
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: territorial extent | Statement: [Acts of Parliament, maySpecify, territorial extent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySpecify Context triple: [Acts of Parliament, maySpecify, territorial extent]
-
A.
mayExtendTo
chosen
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
B.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
C.
mayDelegateTo
Indicates that one entity is permitted to transfer or assign its authority, responsibility, or rights to another entity.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.