Triple
T14139567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribuna stand |
E350386
|
entity |
| Predicate | isHomeSupportArea |
P95639
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tribuna stand, isHomeSupportArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHomeSupportArea Context triple: [Tribuna stand, isHomeSupportArea, true]
-
A.
hasHomeSupport
Indicates that an entity receives assistance, backing, or favorable conditions from its home environment or local supporters.
-
B.
supportArea
chosen
Indicates that one entity serves as a supporting region or surface that provides structural or functional backing for another entity.
-
C.
isResidentialHubIn
Indicates that a location functions primarily as a residential center or hub within a specified larger area or region.
-
D.
hasCustomerAssistanceArea
Indicates that an entity includes or provides a designated area or facility for assisting customers.
-
E.
hasPrimaryServiceArea
Indicates that an entity is associated with a main geographic or functional area in which it primarily provides its services.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6111a36081909beff35c88a56960 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:40 a.m.