Triple
T30103716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Hadn't Anyone Till You |
E765071
|
entity |
| Predicate | isWidelyRecordedSince |
P103301
|
FINISHED |
| Object | late 1930s |
—
|
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: late 1930s | Statement: [I Hadn't Anyone Till You, isWidelyRecordedSince, late 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyRecordedSince Context triple: [I Hadn't Anyone Till You, isWidelyRecordedSince, late 1930s]
-
A.
historicallyRecordedSince
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.
firstWidelyObserved
Indicates that something was initially noticed or recorded by a large number of observers or across a broad context for the first time.
-
C.
wasFirstObservedIn
Indicates that an entity was initially noticed, recorded, or detected at a particular time or place.
-
D.
isFrequentlyRecordedSinceDecade
chosen
Indicates that an entity has been commonly or regularly recorded starting from a specified decade.
-
E.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d96e9288190ae7ec29f4752505c |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:09 p.m.