Triple
T10425791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Youth Institute |
E245781
|
entity |
| Predicate | hasParticipantScope |
P24020
|
FINISHED |
| Object | international |
—
|
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: international | Statement: [Global Youth Institute, hasParticipantScope, international]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticipantScope Context triple: [Global Youth Institute, hasParticipantScope, international]
-
A.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
B.
participantScope
chosen
Indicates the extent, range, or set of participants that are involved in or affected by a given relationship or action.
-
C.
hasBroadcastScope
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
-
D.
hasGlobalParticipation
Indicates that an entity is involved in or contributes to activities, initiatives, or operations that span multiple countries or have worldwide scope.
-
E.
hasScopeRule
Indicates that a given entity is governed, constrained, or interpreted according to a particular scope-defining rule.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea48cb348190ad4432f263300592 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:12 p.m.