Triple
T3418929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache License 1.1 |
E72071
|
entity |
| Predicate | isDeprecatedByPublisher |
P49346
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Apache License 1.1, isDeprecatedByPublisher, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDeprecatedByPublisher Context triple: [Apache License 1.1, isDeprecatedByPublisher, true]
-
A.
deprecatedInVersion
Indicates that something is no longer recommended for use starting from a specified version.
-
B.
discontinuedInVersionOf
Indicates that something (such as a feature, product, or component) ceased to be available or supported starting from a specific version of another entity.
-
C.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
D.
previouslySupported
Indicates that an entity provided support to another entity at some time in the past, but not necessarily in the present.
-
E.
deprecatedInRFC
Indicates that a specification, feature, or practice has been formally marked as deprecated within a particular RFC document.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92df1e48190bbf22a47e44579f1 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb23d23088190aeafe1379eae2eaa |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.