Triple
T30315076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APSL |
E771037
|
entity |
| Predicate | earlierVersionsStatus |
P88993
|
FINISHED |
| Object | incompatible with GNU GPL |
—
|
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: incompatible with GNU GPL | Statement: [APSL, earlierVersionsStatus, incompatible with GNU GPL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierVersionsStatus Context triple: [APSL, earlierVersionsStatus, incompatible with GNU GPL]
-
A.
earlierVersionsCapability
Indicates that an entity has the ability to access, handle, or interact with earlier versions of another entity or resource.
-
B.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
C.
hasVersionStatus
chosen
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
D.
earlierStatus
Indicates that one status or condition occurred or was valid before another status in time.
-
E.
earlierVersionsSponsoredBy
Indicates that earlier versions of an item, work, or entity were financially or otherwise supported by a particular sponsor.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 7:51 p.m.