Triple
T18191860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean-Marie |
E435554
|
entity |
| Predicate | etymologicalOriginOfComponent_Marie |
P5801
|
FINISHED |
| Object | Hebrew name Miryam |
—
|
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: Hebrew name Miryam | Statement: [Jean-Marie, etymologicalOriginOfComponent_Marie, Hebrew name Miryam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologicalOriginOfComponent_Marie Context triple: [Jean-Marie, etymologicalOriginOfComponent_Marie, Hebrew name Miryam]
-
A.
etymologicalRootName
Indicates that one name is derived from, or originates etymologically in, another name.
-
B.
etymologyProposedBy
Indicates that a proposed origin or derivation of a word or term is attributed to a particular person or source.
-
C.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
D.
etymologyReason
Indicates the reason, source, or origin explaining how or why a term acquired its particular etymology.
-
E.
etymologicalSource
chosen
Indicates that one term or name originates from, is derived from, or has its roots in another term or 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d05974819094b4a50d081be881 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.