Triple
T33649799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saltimbanco |
E862062
|
entity |
| Predicate | performedOnContinent |
P128626
|
FINISHED |
| Object | North America |
E335
|
NE 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: North America | Statement: [Saltimbanco, performedOnContinent, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedOnContinent Context triple: [Saltimbanco, performedOnContinent, North America]
-
A.
hasPerformerContinent
Indicates that the performer involved in an event or work is associated with a specific continent.
-
B.
observedInContinent
chosen
Indicates that something has been observed or recorded as occurring within a particular continent.
-
C.
concludedOnContinent
Indicates that an event, process, or activity came to an end at a location situated on a specified continent.
-
D.
livedOnContinent
Indicates that an entity resided for a period of time on a specified continent.
-
E.
continentOfActivity
Indicates the continent on which an entity primarily operates, is active, or conducts its main activities.
- F. None of above.
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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3627119fe081909449fd8b78f76171 |
completed | June 20, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 1, 2026, 1:42 a.m.