Triple
T3533163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Bon Sens |
E74707
|
entity |
| Predicate | positionOnSuperstition |
P48150
|
FINISHED |
| Object | critical |
—
|
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: critical | Statement: [Le Bon Sens, positionOnSuperstition, critical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnSuperstition Context triple: [Le Bon Sens, positionOnSuperstition, critical]
-
A.
hasSuperstition
Indicates that one entity holds or practices a particular superstition related to another entity or concept.
-
B.
positionOnEvil
Indicates a stance or viewpoint an entity holds regarding what is considered evil or morally wrong.
-
C.
positionOnReason
Indicates that one entity holds a particular stance, justification, or rationale concerning another entity or issue.
-
D.
positionInPantheon
Indicates the rank, role, or hierarchical standing that a deity or figure holds within a specific pantheon or religious hierarchy.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9b945481909867d44b810e8b1f |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed7f2ec819085467d281712e0e8 |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:19 p.m.