Triple
T9476398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRT International Children’s Festival |
E228526
|
entity |
| Predicate | attendeeOrigin |
P48015
|
FINISHED |
| Object | many countries |
—
|
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: many countries | Statement: [TRT International Children’s Festival, attendeeOrigin, many countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendeeOrigin Context triple: [TRT International Children’s Festival, attendeeOrigin, many countries]
-
A.
attendeeCountry
Indicates the country associated with an attendee, typically where the attendee comes from or is based.
-
B.
participantsOrigin
chosen
Indicates that the relationship specifies the geographic or organizational origin of the participants involved in an event or activity.
-
C.
typicalVisitorOrigin
Indicates the usual geographic source or location from which visitors to a place, event, or entity most commonly come.
-
D.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
E.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd80127744819082176b2d4417216e |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.