Triple
T36765707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleja Jana Pawła II |
E908331
|
entity |
| Predicate | isCommercialAxisIn |
P93567
|
FINISHED |
| Object | Warsaw |
—
|
NE NERFINISHED |
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: Warsaw | Statement: [Aleja Jana Pawła II, isCommercialAxisIn, Warsaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommercialAxisIn Context triple: [Aleja Jana Pawła II, isCommercialAxisIn, Warsaw]
-
A.
hasCommercialAxis
chosen
Indicates that there exists a primary direction, route, or area along which commercial or business activities are concentrated or organized.
-
B.
isCommercialPort
Indicates that a location functions as a port used for commercial or trade-related maritime activities.
-
C.
isCommercialHubIn
Indicates that a place functions as a primary center of commercial or business activity within a specified larger area or region.
-
D.
isCommercialLinkBetween
Indicates that there exists a commercial relationship or transaction-based connection between the referenced entities.
-
E.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.