Triple
T36405708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Court of Malaysia |
E896743
|
entity |
| Predicate | reconstitutedInYear |
P9623
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Federal Court of Malaysia, reconstitutedInYear, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconstitutedInYear Context triple: [Federal Court of Malaysia, reconstitutedInYear, 1994]
-
A.
reconstitutedFor
Indicates that something has been restored, rebuilt, or reassembled specifically for a particular purpose, use, or context.
-
B.
reconstructionYear
chosen
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
C.
reconstitutionDate
Indicates the date on which something (typically a substance, solution, or entity) is restored or prepared from a prior, preserved, or inactive state.
-
D.
recombinedInYear
Indicates that an entity was recombined, reclassified, or reassigned in a particular year.
-
E.
recoveredYear
Indicates the year in which something that was lost, damaged, or unwell was successfully restored, retrieved, or brought back to a desired state.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.