Triple
T2055451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argosy |
E45663
|
entity |
| Predicate | publishingPeriod |
P3627
|
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: [Argosy, publishingPeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishingPeriod Context triple: [Argosy, publishingPeriod, early 20th century]
-
A.
publicationFrequency
Indicates how often a publication or content is issued, released, or made available over a given period.
-
B.
publicationPeriod
chosen
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
C.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
D.
circulationPeriod
Indicates the length of time during which an item is allowed to be borrowed, used, or remain in active circulation before it must be returned, renewed, or retired.
-
E.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9a9ce548190a5a3488fafb2e79e |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.