Triple
T4942315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Courses in Public International Law |
E110967
|
entity |
| Predicate | participantsFrom |
P30745
|
FINISHED |
| Object | countries worldwide |
—
|
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: countries worldwide | Statement: [Summer Courses in Public International Law, participantsFrom, countries worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantsFrom Context triple: [Summer Courses in Public International Law, participantsFrom, countries worldwide]
-
A.
participantFrom
chosen
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
B.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
C.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
D.
participant
Indicates that an entity takes part in, is involved in, or plays a role within a specified event, activity, or process.
-
E.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70a5f56481908365d0fe16892bf4 |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.