Triple
T38284324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Street Fire Station |
E1022161
|
entity |
| Predicate | guestAccess |
P79603
|
FINISHED |
| Object | walk-through area |
—
|
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: walk-through area | Statement: [Main Street Fire Station, guestAccess, walk-through area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestAccess Context triple: [Main Street Fire Station, guestAccess, walk-through area]
-
A.
guestFlow
Indicates the movement or progression of guests through a space, process, or experience over time.
-
B.
guestRole
Indicates that one entity participates in or is associated with another entity in the capacity of a guest, specifying the nature or type of that guest participation.
-
C.
allowsGuests
Indicates that an entity permits other people, not part of its primary group or membership, to be present or participate.
-
D.
visitorAccessPoint
chosen
Indicates a location or interface through which visitors are allowed to enter, connect, or gain access to a place, system, or resource.
-
E.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.