Triple
T19470844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John-Paul |
E487117
|
entity |
| Predicate | etymologyLanguageOfComponentPaul |
P136048
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [John-Paul, etymologyLanguageOfComponentPaul, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyLanguageOfComponentPaul Context triple: [John-Paul, etymologyLanguageOfComponentPaul, Latin]
-
A.
etymologyProposedBy
Indicates that a proposed origin or derivation of a word or term is attributed to a particular person or source.
-
B.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
C.
patronymicOrigin
Indicates that one entity’s name is derived from the name of a father or paternal ancestor of another entity.
-
D.
etymologyPossibleMeaning
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
E.
popularEtymology
Indicates that an etymological explanation is based on common belief or folk interpretation rather than on historically or linguistically accurate origins.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e809008190b0021d41b99f9700 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:39 p.m.