Triple
T23471057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organisation internationale de la Francophonie |
E570127
|
entity |
| Predicate | observerStateCount |
P152401
|
FINISHED |
| Object | 27 |
—
|
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: 27 | Statement: [Organisation internationale de la Francophonie, observerStateCount, 27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observerStateCount Context triple: [Organisation internationale de la Francophonie, observerStateCount, 27]
-
A.
observerState
Indicates the condition, status, or configuration an observer is in at the time it perceives or monitors something.
-
B.
observerStatusIn
Indicates that an entity’s status or role is defined or valid within a specified observational context, system, or environment.
-
C.
hasObserverStates
Indicates that an entity is associated with one or more observer-specific states or conditions under which it is perceived or evaluated.
-
D.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
E.
isObservedOn
Indicates that a particular phenomenon, condition, or attribute is detected or recorded at a specific time, date, or occasion.
- F. None of above. chosen
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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6ff8dc0819086961b1f07030d9c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:55 p.m.