Triple
T7236830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica Hudson |
E155249
|
entity |
| Predicate | usesSpaceFor |
P61443
|
FINISHED |
| Object | large-scale performances |
—
|
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: large-scale performances | Statement: [Basilica Hudson, usesSpaceFor, large-scale performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSpaceFor Context triple: [Basilica Hudson, usesSpaceFor, large-scale performances]
-
A.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
B.
usesCodeSpace
Indicates that one entity employs or operates within a particular code space or coding environment provided by another entity.
-
C.
spaceUsage
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
-
D.
publicSpacesUsed
chosen
Indicates that certain public spaces are being utilized or occupied for a particular purpose or activity.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:55 p.m.