Triple
T18512491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Mile Act 1665 |
E452375
|
entity |
| Predicate | prohibitedFromApproaching |
P38719
|
FINISHED |
| Object | incorporated towns |
—
|
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: incorporated towns | Statement: [Five Mile Act 1665, prohibitedFromApproaching, incorporated towns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitedFromApproaching Context triple: [Five Mile Act 1665, prohibitedFromApproaching, incorporated towns]
-
A.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
B.
isProhibitedFor
chosen
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
C.
seeksToAvoid
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
D.
awayFrom
Indicates that one entity is located at a distance from, or moving farther away from, another entity.
-
E.
prohibitedWeapon
Indicates that an entity is classified as a weapon whose possession, use, or transfer is forbidden by law, regulation, or policy.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53346f9488190bc2e4570564bede0 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.