Triple
T37686990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AnnaBeth |
E938394
|
entity |
| Predicate | nameElementMeaning_Beth |
P181286
|
FINISHED |
| Object | pledged to God |
—
|
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: pledged to God | Statement: [AnnaBeth, nameElementMeaning_Beth, pledged to God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameElementMeaning_Beth Context triple: [AnnaBeth, nameElementMeaning_Beth, pledged to God]
-
A.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
B.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
C.
possibleNameMeaning
chosen
Indicates that a given interpretation or semantic meaning is a plausible or potential meaning of a specified name.
-
D.
namingMeaning
Indicates that one entity provides the meaning, sense, or semantic interpretation of a given name or naming expression for another entity.
-
E.
nameComponentFortMeaning
Indicates that a component of a name expresses or carries the meaning associated with a fort.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.