Triple
T50978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman-Dutch law |
E999
|
entity |
| Predicate | combinedWith |
P402
|
FINISHED |
| Object | English common law (in South Africa) |
—
|
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: English common law (in South Africa) | Statement: [Roman-Dutch law, combinedWith, English common law (in South Africa)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinedWith Context triple: [Roman-Dutch law, combinedWith, English common law (in South Africa)]
-
A.
formedByUnionOf
chosen
Indicates that something is created or defined as the union or combination of multiple other things.
-
B.
composedBy
Indicates that one entity is the creator or author of a musical or artistic work associated with another entity.
-
C.
mergedInto
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
D.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
E.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac23f04819080cef9365ed990d4 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.