Triple
T35432965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doctrinaires |
E1024115
|
entity |
| Predicate | positionOnPress |
P127126
|
FINISHED |
| Object | relative freedom of the press |
—
|
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: relative freedom of the press | Statement: [Doctrinaires, positionOnPress, relative freedom of the press]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnPress Context triple: [Doctrinaires, positionOnPress, relative freedom of the press]
-
A.
positionOnRelease
Indicates the spatial position or location of an entity at the moment it is released.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
positionOnBehavior
chosen
Indicates the stance, attitude, or viewpoint one entity holds regarding another entity’s behavior or conduct.
-
D.
positionOnChange
Indicates that one entity’s position is altered or updated as a result of a change event or transition.
-
E.
positionOnSystem
Indicates the relative location or placement of an entity within a larger structured system or framework.
- 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.