Triple
T3729504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (15760) 1992 QB1 |
E79026
|
entity |
| Predicate | epochOfFirstRecognitionAsKBO |
P23896
|
FINISHED |
| Object | early 1990s |
—
|
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 1990s | Statement: [(15760) 1992 QB1, epochOfFirstRecognitionAsKBO, early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epochOfFirstRecognitionAsKBO Context triple: [(15760) 1992 QB1, epochOfFirstRecognitionAsKBO, early 1990s]
-
A.
recognitionDate
chosen
Indicates the date on which an entity, status, or achievement is formally acknowledged or officially recognized.
-
B.
firstCelebratedInYear
Indicates the year in which something (such as an event, holiday, or celebration) was first observed or celebrated.
-
C.
recognizedSince
Indicates that one entity has formally acknowledged, accepted, or identified another entity as valid or legitimate starting from a specific point in time.
-
D.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
-
E.
firstYearUnderCurrentName
Indicates the first year in which an entity began operating or being known under its current name.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb17432881909390284b935ed3fd |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.