Triple
T18952894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sky Ladder |
E463698
|
entity |
| Predicate | dateOfFinalRealization |
P82025
|
FINISHED |
| Object | 2015-06-15 |
—
|
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: 2015-06-15 | Statement: [Sky Ladder, dateOfFinalRealization, 2015-06-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFinalRealization Context triple: [Sky Ladder, dateOfFinalRealization, 2015-06-15]
-
A.
dateFinalized
chosen
Indicates that a specific date has been set as the official or final completion/confirmation time for an associated event, decision, or record.
-
B.
finalRealization
Indicates the culminating recognition or understanding that occurs at the end of a process, event, or sequence of actions.
-
C.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
D.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
E.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d544fef8819091147189ddd89617 |
completed | April 20, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon