Triple
T23825697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Why Georgia |
E589365
|
entity |
| Predicate | timePeriodOfRecording |
P44812
|
FINISHED |
| Object | early 2000s |
—
|
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 2000s | Statement: [Why Georgia, timePeriodOfRecording, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfRecording Context triple: [Why Georgia, timePeriodOfRecording, early 2000s]
-
A.
recordDuration
Indicates the length of time for which something is recorded or captured.
-
B.
mainRecordingPeriod
chosen
Indicates the primary time span during which the recording activity took place.
-
C.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
D.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
E.
includesRecordingPeriod
Indicates that one entity encompasses or specifies the time span during which another entity was recorded or observed.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f114cc8190a8a557b7fd12c5c6 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8 p.m.