Triple
T9056291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Froggie Went A-Courtin’ |
E217005
|
entity |
| Predicate | hasEarliestKnownPrint |
P23833
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Froggie Went A-Courtin’, hasEarliestKnownPrint, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarliestKnownPrint Context triple: [Froggie Went A-Courtin’, hasEarliestKnownPrint, 16th century]
-
A.
printedFirstEditionOf
Indicates that the subject entity produced and issued the initial published edition of the object entity.
-
B.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
-
C.
earliestManuscripts
chosen
Indicates that the related entity (e.g., a text or work) is associated with its earliest known surviving manuscripts or documentary witnesses.
-
D.
hasEarliestMajorCorpus
Indicates that one entity is associated with the earliest significant or primary body of work (major corpus) relative to other comparable entities.
-
E.
firstPrintedInPlace
Indicates the place where an item (such as a work or edition) was first printed.
- 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_69ca83d4425481909a319dab847724ec |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a75d8e881909414d745ec054182 |
completed | April 1, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee6d83c819095d8ed0779aa8511 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.