Triple
T27327496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Weber |
E689696
|
entity |
| Predicate | hasNamePartMeaning |
P24069
|
FINISHED |
| Object | Johann means "Yahweh is gracious" |
—
|
NE NERFINISHED |
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: Johann means "Yahweh is gracious" | Statement: [Johann Weber, hasNamePartMeaning, Johann means "Yahweh is gracious"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamePartMeaning Context triple: [Johann Weber, hasNamePartMeaning, Johann means "Yahweh is gracious"]
-
A.
hasNameMeaningRelation
Indicates that there is a relationship between an entity and a name that conveys or encodes a particular meaning or significance.
-
B.
hasGivenNameMeaning
chosen
Indicates that a given name carries a particular meaning or semantic interpretation.
-
C.
hasBaseNameMeaning
Indicates that an entity’s base name carries or is associated with a particular meaning.
-
D.
nameComponentFortMeaning
Indicates that a component of a name expresses or carries the meaning associated with a fort.
-
E.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 27, 2026, 11:36 a.m.