Triple
T17290399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Seals |
E419767
|
entity |
| Predicate | Seal of the Mouth |
P126833
|
FINISHED |
| Object | prohibits false speech |
—
|
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: prohibits false speech | Statement: [Three Seals, Seal of the Mouth, prohibits false speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Seal of the Mouth Context triple: [Three Seals, Seal of the Mouth, prohibits false speech]
-
A.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
B.
fromMouth
Indicates that something originates from or is emitted out of a mouth.
-
C.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
D.
mouthCharacteristic
Indicates that an entity has a specific property, feature, or quality related to its mouth.
-
E.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e437837d048190949b947f5437636d |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.