Triple
T30315077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APSL |
E771037
|
entity |
| Predicate | laterVersionsStatus |
P88993
|
FINISHED |
| Object | less restrictive than earlier versions |
—
|
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: less restrictive than earlier versions | Statement: [APSL, laterVersionsStatus, less restrictive than earlier versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterVersionsStatus Context triple: [APSL, laterVersionsStatus, less restrictive than earlier versions]
-
A.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
B.
laterVersionsCapability
Indicates that one entity has the capability to support, handle, or be compatible with later versions of another entity.
-
C.
hasVersionStatus
chosen
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
D.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
E.
hasSubsequentVersion
Indicates that one entity is a later or updated version that follows another entity in a version sequence.
- 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_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: April 29, 2026, 7:51 p.m.