Triple
T21584749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue House |
E532618
|
entity |
| Predicate | previouslyRestrictedArea |
P63323
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Blue House, previouslyRestrictedArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyRestrictedArea Context triple: [Blue House, previouslyRestrictedArea, yes]
-
A.
previouslyOutside
Indicates that an entity was located outside a specified area or boundary at some earlier time prior to the current reference point.
-
B.
regulatedArea
chosen
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
C.
previouslyAllowed
Indicates that an action or relationship was permitted at some earlier time, though it may not be allowed now.
-
D.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
-
E.
previouslySurroundedBy
Indicates that an entity was, at some earlier time, completely encircled or enclosed by another entity or group of entities.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5f2cc0819095552de70eb2ad8d |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.