Triple
T37798068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Cecilia Square |
E942287
|
entity |
| Predicate | isLikelyToFeature |
P53912
|
FINISHED |
| Object | musical 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: musical performances | Statement: [Saint Cecilia Square, isLikelyToFeature, musical performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLikelyToFeature Context triple: [Saint Cecilia Square, isLikelyToFeature, musical performances]
-
A.
isFeatureRich
Indicates that an entity possesses a large number and wide variety of capabilities or functionalities.
-
B.
isFeatureBased
Indicates that one entity is derived from, determined by, or constructed using the characteristics or attributes of another entity.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
mayIncludeFeature
chosen
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
E.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.