Triple
T16233298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marriage Law of the People's Republic of China |
E394041
|
entity |
| Predicate | secondMajorRevisionDate |
P24446
|
FINISHED |
| Object | 2001-04-28 |
—
|
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-04-28 | Statement: [Marriage Law of the People's Republic of China, secondMajorRevisionDate, 2001-04-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondMajorRevisionDate Context triple: [Marriage Law of the People's Republic of China, secondMajorRevisionDate, 2001-04-28]
-
A.
majorRevisionDate
chosen
Indicates the date on which an entity underwent a significant or substantial update or revision.
-
B.
secondMajorLawDate
Indicates the date on which an entity’s second major law, statute, or significant legal act was enacted or came into effect.
-
C.
secondReachedDate
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
D.
secondVersion
Indicates that one entity is a later or updated second version of another entity.
-
E.
secondApparitionDate
Indicates the date on which an entity appeared or manifested for the second time.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d2b0cc48190853919135d5a172a |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.