Triple
T23214085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Door |
E580682
|
entity |
| Predicate | hasRecordingDate |
P38643
|
FINISHED |
| Object | early 1980s |
—
|
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 1980s | Statement: [Green Door, hasRecordingDate, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecordingDate Context triple: [Green Door, hasRecordingDate, early 1980s]
-
A.
recordedOnDate
Indicates the specific calendar date on which an event, action, or piece of information was formally recorded.
-
B.
hasCaptureDate
chosen
Indicates the date on which something (such as an image, video, or data sample) was originally captured or recorded.
-
C.
recordSettingDate
Indicates the date on which a particular record was established, set, or officially recorded.
-
D.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
-
E.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f19163b9b88190a68fa6d08d37bdb7 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:07 p.m.