Triple
T9773258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford Designer Outlet |
E237176
|
entity |
| Predicate | hasCustomerFacility |
P12416
|
FINISHED |
| Object | toilets |
—
|
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: toilets | Statement: [Ashford Designer Outlet, hasCustomerFacility, toilets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerFacility Context triple: [Ashford Designer Outlet, hasCustomerFacility, toilets]
-
A.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
C.
hasCompanyFacility
Indicates that a company possesses, operates, or is responsible for a particular facility.
-
D.
hasTerminalFacility
Indicates that an entity possesses or includes a terminal facility used as an endpoint for transport, communication, or related operations.
-
E.
ownsFacilityOn
Indicates that one entity possesses ownership or control over a facility located on or associated with another entity (such as a site, property, or area).
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f6b8348190bd05b94519de9bc9 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.