Triple
T20268634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary |
E499032
|
entity |
| Predicate | etymologyPossiblyDerivedFrom |
P5801
|
FINISHED |
| Object | place name Gary in France |
—
|
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: place name Gary in France | Statement: [Gary, etymologyPossiblyDerivedFrom, place name Gary in France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyPossiblyDerivedFrom Context triple: [Gary, etymologyPossiblyDerivedFrom, place name Gary in France]
-
A.
etymologyPossibleMeaning
Indicates a possible or hypothesized meaning that an etymological analysis suggests for a word or term.
-
B.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
C.
etymologicalSource
chosen
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
D.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
E.
etymologyProposedBy
Indicates that a proposed origin or derivation of a word or term is attributed to a particular person or source.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e675dbb7ac8190a40c527f2c02ca50 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:42 p.m.