Triple
T19777571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unclaimed Baggage Center |
E475042
|
entity |
| Predicate | hasApproximateCustomerBase |
P3846
|
FINISHED |
| Object | regional visitors |
—
|
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: regional visitors | Statement: [Unclaimed Baggage Center, hasApproximateCustomerBase, regional visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateCustomerBase Context triple: [Unclaimed Baggage Center, hasApproximateCustomerBase, regional visitors]
-
A.
hasCustomers
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
B.
exportCustomersCountEstimate
Indicates an estimated number of customers included in an export operation.
-
C.
hasApproximateNumberOfPeople
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
-
D.
approximateAudienceSize
chosen
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
E.
hasApproximateVendorCount
Indicates that an entity is associated with an estimated or non-exact number of vendors.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65361a8e08190b52944aab25e45fa |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.