Triple
T36990717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinah |
E915087
|
entity |
| Predicate | hasRecordingHistoryStartingIn |
—
|
GENERATED |
| Object | 1920s |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingHistoryStartingIn Context triple: [Dinah, hasRecordingHistoryStartingIn, 1920s]
-
A.
hasRecordingHistory
Indicates that an entity has an associated record of past recordings or recorded events.
-
B.
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.
-
C.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
D.
hasRecordingLegacy
Indicates that an entity is associated with a historical or prior version of a recording, capturing its legacy or earlier state.
-
E.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
- F. None of above.
Provenance (1 batch)
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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.