Triple
T6004433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet Caporal |
E133674
|
entity |
| Predicate | timePeriodOfCardIssues |
P302
|
FINISHED |
| Object | early 1900s |
—
|
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 1900s | Statement: [Sweet Caporal, timePeriodOfCardIssues, early 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfCardIssues Context triple: [Sweet Caporal, timePeriodOfCardIssues, early 1900s]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
-
C.
hasValidityPeriodAnonymousCard
Indicates that an anonymous card is associated with a specific time period during which it is valid or usable.
-
D.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
E.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f10d18081908c351170b7f58d3d |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.