Triple
T572897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Brother Island |
E13699
|
entity |
| Predicate | hasLegalRestriction |
P10734
|
FINISHED |
| Object | no general public landing |
—
|
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: no general public landing | Statement: [South Brother Island, hasLegalRestriction, no general public landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalRestriction Context triple: [South Brother Island, hasLegalRestriction, no general public landing]
-
A.
formerLegalRestriction
Indicates that a legal restriction once applied to an entity or relationship but is no longer in effect.
-
B.
notableRestriction
chosen
Indicates that there is a significant limitation, constraint, or prohibition that meaningfully affects the entity or its use.
-
C.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
hasLegalEffect
Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b49bad88190bc73d31a317c0ef4 |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.