Triple
T16233362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tort Liability Law of the People's Republic of China |
E394042
|
entity |
| Predicate | systematicRole |
P12085
|
FINISHED |
| Object | laid foundation for modern tort law in China |
—
|
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: laid foundation for modern tort law in China | Statement: [Tort Liability Law of the People's Republic of China, systematicRole, laid foundation for modern tort law in China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systematicRole Context triple: [Tort Liability Law of the People's Republic of China, systematicRole, laid foundation for modern tort law in China]
-
A.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
B.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
-
D.
systemRole
chosen
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
E.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
- 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_69e23d2be2f881908ec2483507cb0b00 |
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.