Triple
T9112275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benny |
E218630
|
entity |
| Predicate | originalNameMeaningSource |
P86557
|
FINISHED |
| Object | Benedict meaning "blessed" |
—
|
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: Benedict meaning "blessed" | Statement: [Benny, originalNameMeaningSource, Benedict meaning "blessed"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNameMeaningSource Context triple: [Benny, originalNameMeaningSource, Benedict meaning "blessed"]
-
A.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
B.
formerNameMeaning
Indicates that the meaning or interpretation of an entity’s previous name is being specified.
-
C.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
D.
originalNameLanguage
Indicates that the specified language is the language in which an entity’s original or primary name was expressed.
-
E.
officialNameMeaning
Indicates the semantic meaning or etymological significance conveyed by an entity’s official name.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8495c448190b9bb3803fb2dda70 |
completed | April 1, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:16 p.m.