Triple
T5753175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arte Moreno |
E126899
|
entity |
| Predicate | announcedExplorationOfSale |
P62875
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Arte Moreno, announcedExplorationOfSale, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedExplorationOfSale Context triple: [Arte Moreno, announcedExplorationOfSale, 2022]
-
A.
saleAnnouncedIn
Indicates that the occurrence or details of a sale are publicly communicated or reported within a particular medium, document, or announcement.
-
B.
publiclyAnnouncedBy
chosen
Indicates that an action, decision, or piece of information was formally communicated to the public by a specified agent or entity.
-
C.
announcedCraftsmanSale
Indicates that an entity has publicly communicated or declared the occurrence of a sale involving a craftsman or craftsman-related goods or services.
-
D.
subjectOfSale
Indicates that one entity is the item, asset, or right being transferred or offered in a sale transaction involving another entity.
-
E.
announcedThrough
Indicates that an announcement or communication was made via a particular medium, channel, or intermediary.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.