Triple
T11594746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungarian Dances |
E274971
|
entity |
| Predicate | recordedSince |
P6054
|
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: [Hungarian Dances, recordedSince, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedSince Context triple: [Hungarian Dances, recordedSince, early 20th century]
-
A.
historicallyRecordedSince
chosen
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
-
B.
recordedBetween
Indicates that an event or data item was recorded at a time that falls within a specified start and end time interval.
-
C.
recordedOnDate
Indicates the specific calendar date on which an event, action, or piece of information was formally recorded.
-
D.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
E.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946790d08190924d60bb4b523250 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.