Triple
T19218210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corteo |
E480540
|
entity |
| Predicate | setElement |
P135023
|
FINISHED |
| Object | central rotating stage |
—
|
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: central rotating stage | Statement: [Corteo, setElement, central rotating stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setElement Context triple: [Corteo, setElement, central rotating stage]
-
A.
setWith
Indicates that one entity is grouped, combined, or associated together in a set or collection with another entity.
-
B.
setsReferenceValue
Indicates that one entity assigns or establishes a reference value to be used as a standard or baseline for another entity or process.
-
C.
setInto
Indicates placing or inserting one entity into another entity or context, often initiating a new state or condition.
-
D.
setInEvent
Indicates that an entity is situated within, occurs during, or is contextually located in a particular event.
-
E.
setRecordAt
Indicates assigning or updating a record at a specific position or location within a collection or data structure.
- F. None of above. chosen
Provenance (4 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3c552c8190b22844e5b7adfc50 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:23 p.m.