Triple
T1168220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hick from French Lick |
E24848
|
entity |
| Predicate | highlightsTrait |
P662
|
FINISHED |
| Object | small-town roots |
—
|
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: small-town roots | Statement: [The Hick from French Lick, highlightsTrait, small-town roots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlightsTrait Context triple: [The Hick from French Lick, highlightsTrait, small-town roots]
-
A.
highlights
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
B.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
C.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
D.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
notableAdvantage
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccef84481908864e819884af86c |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.