Triple
T32430657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Simmons |
E828712
|
entity |
| Predicate | hasNamePartOrigin |
P3325
|
FINISHED |
| Object | Michael is of Hebrew origin |
—
|
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: Michael is of Hebrew origin | Statement: [Michael Simmons, hasNamePartOrigin, Michael is of Hebrew origin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamePartOrigin Context triple: [Michael Simmons, hasNamePartOrigin, Michael is of Hebrew origin]
-
A.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
C.
hasUncertainOriginalName
Indicates that the entity’s original name is not known with certainty or is subject to doubt or ambiguity.
-
D.
hasEpithetOrigin
Indicates that the origin or source of an epithet (a descriptive name or label) is specified for an entity.
-
E.
hasGivenNameBasis
Indicates that one entity’s given name is derived from, based on, or formed using another entity (such as a name, word, or person) as its basis.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 1, 2026, 12:55 a.m.