Triple
T1220106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gage |
E26199
|
entity |
| Predicate | hasMeaningRelatedTo |
P12753
|
FINISHED |
| Object | pledge |
—
|
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: pledge | Statement: [Gage, hasMeaningRelatedTo, pledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningRelatedTo Context triple: [Gage, hasMeaningRelatedTo, pledge]
-
A.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
B.
possibleMeaning
Indicates that something may plausibly represent, signify, or be interpreted as a particular meaning or sense.
-
C.
semanticRelation
chosen
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
D.
sharesMeaningWith
Indicates that two expressions convey the same or very similar meaning, even if they differ in form or wording.
-
E.
meaningComponent
Indicates that one entity represents a semantic or conceptual component contributing to the overall meaning of another entity.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be1ead088190bf44dc6ab1edf18b |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.