Triple
T6432032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenesaw |
E129799
|
entity |
| Predicate | hasNotableTimePeriodOfProminence |
P24496
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Kenesaw, hasNotableTimePeriodOfProminence, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTimePeriodOfProminence Context triple: [Kenesaw, hasNotableTimePeriodOfProminence, early 20th century]
-
A.
hadPeakInfluencePeriod
Indicates the time span during which an entity exerted its greatest or most significant influence.
-
B.
wasProminentIn
chosen
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
C.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
D.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
E.
hasNotablePerformance
Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular 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_69c0084caac48190a7bc2ad8ba44536f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693cadf08190aca84888a3440b3d |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.