Triple
T8361507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bid Time Return |
E197016
|
entity |
| Predicate | timePeriodVisited |
P26942
|
FINISHED |
| Object | 1890s |
—
|
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: 1890s | Statement: [Bid Time Return, timePeriodVisited, 1890s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodVisited Context triple: [Bid Time Return, timePeriodVisited, 1890s]
-
A.
scopeOfVisits
Indicates the range, extent, or boundaries within which visits or visiting activities occur or are applicable.
-
B.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
C.
visitedDuring
chosen
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
-
D.
timeSincePreviousVisitMentioned
Indicates that the elapsed time since a previous visit is explicitly referenced or specified in the context.
-
E.
bestVisitedAt
Indicates the optimal time or conditions under which a place or entity should be visited.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8074e4588190b394d1622adca2cb |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.