Triple
T4689958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PolioPlus |
E104009
|
entity |
| Predicate | mobilizes |
P58818
|
FINISHED |
| Object | Rotary volunteers |
—
|
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: Rotary volunteers | Statement: [PolioPlus, mobilizes, Rotary volunteers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobilizes Context triple: [PolioPlus, mobilizes, Rotary volunteers]
-
A.
mobilization
Indicates the process by which entities are organized, activated, or assembled to take coordinated action or move into a state of readiness.
-
B.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
C.
mobilizationCentre
Indicates a location where resources, personnel, or equipment are gathered and organized in preparation for deployment or coordinated action.
-
D.
canBeMobilisedFor
Indicates that an entity is capable of being called upon, activated, or deployed for a particular purpose, task, or operation.
-
E.
mobilizationAuthority
Indicates the entity that has the formal power or responsibility to initiate, direct, or authorize the mobilization of resources, personnel, or assets.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd660414b08190ab37467755d383b5 |
completed | March 20, 2026, 3:21 p.m. |
Created at: March 20, 2026, 1:16 p.m.