Triple
T17786598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | This is propaganda |
E444031
|
entity |
| Predicate | collectingMode |
P100170
|
FINISHED |
| Object | sold as a set of oral instructions |
—
|
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: sold as a set of oral instructions | Statement: [This is propaganda, collectingMode, sold as a set of oral instructions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectingMode Context triple: [This is propaganda, collectingMode, sold as a set of oral instructions]
-
A.
collectingStatus
Indicates the current state or phase of an ongoing collection process or activity.
-
B.
collectingAllowed
Indicates whether an entity is permitted to collect or gather specified items, data, or resources.
-
C.
acquisitionMode
chosen
Indicates the method or process by which one entity obtains, receives, or gains another entity or resource.
-
D.
canCollect
Indicates that one entity has the ability or permission to gather, receive, or take possession of another entity.
-
E.
collectedWith
Indicates that one entity was gathered, acquired, or obtained together with another entity as part of the same collection event or process.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487938418819096016ad717b014e6 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.