Triple
T4582279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NDCs |
E101881
|
entity |
| Predicate | firstSubmissionPeriod |
P43266
|
FINISHED |
| Object | around 2015–2016 |
—
|
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: around 2015–2016 | Statement: [NDCs, firstSubmissionPeriod, around 2015–2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSubmissionPeriod Context triple: [NDCs, firstSubmissionPeriod, around 2015–2016]
-
A.
launchPeriod
Indicates the time span during which a launch or deployment activity occurs or is valid.
-
B.
firstTimeParticipation
Indicates that an entity is taking part in a specified event, activity, or context for the very first time.
-
C.
acceptsSubmissionsFrom
Indicates that one entity receives and is willing to consider submissions (such as content, proposals, or applications) originating from another entity.
-
D.
firstMintingPeriodStart
Indicates the point in time when the initial minting period for a given asset or token begins.
-
E.
registrationPeriod
chosen
Indicates the time span during which registration for something is open or 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59029568819091db1e77a9a2ec41 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.