Triple
T15886264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSCE Forum for Security Co-operation |
E385199
|
entity |
| Predicate | hasNumberOfParticipatingStates |
P244
|
FINISHED |
| Object | 57 |
—
|
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: 57 | Statement: [OSCE Forum for Security Co-operation, hasNumberOfParticipatingStates, 57]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfParticipatingStates Context triple: [OSCE Forum for Security Co-operation, hasNumberOfParticipatingStates, 57]
-
A.
hasNumberOfStatesAndDistricts
Indicates a relationship where an entity is associated with a specific count of its constituent states and districts.
-
B.
hasMembersPerState
Indicates a relationship that specifies how many members are associated with each state.
-
C.
participatingState
Indicates that a state is taking part in, or is formally involved as a participant in, a specified event, process, or arrangement.
-
D.
numberOfStates
chosen
Indicates the total count of distinct states or conditions associated with an entity or system.
-
E.
hasTwoDistrictsInState
Indicates that an entity is associated with exactly two distinct districts within a specified state.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.