Triple
T14930893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache License 1.0 |
E372260
|
entity |
| Predicate | includesAdvertisingClause |
P116712
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Apache License 1.0, includesAdvertisingClause, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAdvertisingClause Context triple: [Apache License 1.0, includesAdvertisingClause, yes]
-
A.
hasNoAdvertisingClause
Indicates that an agreement or contract does not contain any clause restricting or prohibiting advertising.
-
B.
usesAdvertisingModel
Indicates that one entity employs or relies on another entity’s advertising-based business or revenue model.
-
C.
hasAdvertisingVisual
Indicates that an entity includes, is associated with, or uses a specific visual element or asset for advertising purposes.
-
D.
advertisingRestricted
Indicates that there are limitations or prohibitions on advertising activities associated with the related entities.
-
E.
advertises
Indicates that one entity promotes, publicizes, or markets another entity, typically to attract attention or customers.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64550dc8190ba44120df00ba498 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:36 a.m.