Triple
T50974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman-Dutch law |
E999
|
entity |
| Predicate | mainlyCovers |
P380
|
FINISHED |
| Object | private law |
—
|
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: private law | Statement: [Roman-Dutch law, mainlyCovers, private law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainlyCovers Context triple: [Roman-Dutch law, mainlyCovers, private law]
-
A.
hasPartInDiscography
Indicates that an entity (such as a song, album, or track) is included as a component within another entity’s discography.
-
B.
associatedMusic
Indicates a relationship where one entity is linked to or connected with a piece of music, such as being used by, related to, or thematically tied to that music.
-
C.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
D.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
E.
isAbout
chosen
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by 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_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.