Triple
T35648215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokan stock |
E1030064
|
entity |
| Predicate | hasTimePeriodOfProposal |
P9416
|
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: [Hokan stock, hasTimePeriodOfProposal, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodOfProposal Context triple: [Hokan stock, hasTimePeriodOfProposal, early 20th century]
-
A.
timePeriodProposed
chosen
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
B.
hasPeriodOf
Indicates that one entity possesses, experiences, or is associated with a specific span or interval of time.
-
C.
hasPlanningPeriod
Indicates that an entity is associated with a defined time span allocated for planning activities.
-
D.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
E.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 3, 2026, 4:05 p.m.