Triple
T24246183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No One Else Comes Close |
E603377
|
entity |
| Predicate | laterCoveredOn |
P56452
|
FINISHED |
| Object | Millennium |
—
|
NE NERFINISHED |
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: Millennium | Statement: [No One Else Comes Close, laterCoveredOn, Millennium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCoveredOn Context triple: [No One Else Comes Close, laterCoveredOn, Millennium]
-
A.
previouslyCoveredBy
Indicates that something was earlier protected, enclosed, or overlaid by another object or material, but is no longer in that state.
-
B.
laterIncludedOn
chosen
Indicates that one entity was added to, incorporated into, or featured on another entity at a subsequent time.
-
C.
coveredSince
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
-
D.
hasBeenCoveredBy
Indicates that something has received coverage or treatment by another entity, such as being reported on, discussed, or addressed.
-
E.
laterEditionContains
Indicates that a later edition of a work includes all or part of the content from an earlier edition.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b85349481909c21dacd48df7b8e |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:04 a.m.