Triple
T7421701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laws for the Internet Age |
E171263
|
entity |
| Predicate | usedInWorkSubject |
P7040
|
FINISHED |
| Object | copyright 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: copyright law | Statement: [Laws for the Internet Age, usedInWorkSubject, copyright law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInWorkSubject Context triple: [Laws for the Internet Age, usedInWorkSubject, copyright law]
-
A.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
B.
workUsedAs
Indicates that one work is employed or utilized in the creation, performance, or presentation of another work.
-
C.
hasWorkAsSubject
Indicates that an entity serves as the subject (creator or originator) of a particular work or creative output.
-
D.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of another entity.
-
E.
subjectOfWork
chosen
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ebc520819087cfc2eb9dda0e17 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f03648d08190b862d07fef71210c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.