Triple
T1888065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Culture |
E41805
|
entity |
| Predicate | mainArgument |
P33058
|
FINISHED |
| Object | contemporary copyright law is overly restrictive |
—
|
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: contemporary copyright law is overly restrictive | Statement: [Free Culture, mainArgument, contemporary copyright law is overly restrictive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainArgument Context triple: [Free Culture, mainArgument, contemporary copyright law is overly restrictive]
-
A.
mainFunctions
Indicates that the subject serves as the primary or central functional component or role for the object.
-
B.
mainSingle
Indicates that an entity is the primary or sole main instance among a set of related entities.
-
C.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
D.
mainEntranceOn
Indicates that the primary entrance of one entity is located on or faces toward another entity, such as a particular side, street, or boundary.
-
E.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
- F. None of above. chosen
Provenance (4 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb12382b481908cd26b56f8558226 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb11bfd2c8190a805372589f73238 |
completed | March 7, 2026, 5:01 a.m. |
Created at: March 4, 2026, 7:34 p.m.