Triple
T575282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache License 2.0 |
E13748
|
entity |
| Predicate | requiresSourceDisclosure |
P16204
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Apache License 2.0, requiresSourceDisclosure, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSourceDisclosure Context triple: [Apache License 2.0, requiresSourceDisclosure, false]
-
A.
discloses
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
B.
visibilityRequirement
Indicates that one entity must be visible or perceivable under specified conditions for another entity, action, or rule to apply.
-
C.
requiresShowing
Indicates that one entity must be displayed or made visible as a prerequisite or condition for another entity, action, or state.
-
D.
requiresReportTo
Indicates that one entity is obligated to submit or provide a report to another entity.
-
E.
requiresDispositionOf
Indicates that one entity must be appropriately handled, removed, or otherwise disposed of as a condition related to another entity or situation.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b67395c8190a8046ff7debe9d1f |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c4969c819080375d08f9eec50c |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a498dd579081908e02368a4c5efc8c |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:33 p.m.