Triple
T10330413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLink |
E242857
|
entity |
| Predicate | recommendationDate |
P65519
|
FINISHED |
| Object | 2001-06-27 |
—
|
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: 2001-06-27 | Statement: [XLink, recommendationDate, 2001-06-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendationDate Context triple: [XLink, recommendationDate, 2001-06-27]
-
A.
recommendedDate
chosen
Indicates the date on which something is advised or suggested to occur, be used, or be acted upon.
-
B.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
C.
retrievalDate
Indicates the date on which an item, record, or resource was accessed, obtained, or retrieved.
-
D.
recommendedIn
Indicates that one entity is suggested or endorsed within the context, content, or scope of another entity (such as a document, list, or recommendation source).
-
E.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7fb77348190ac8ff887f6f03450 |
completed | April 7, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.