Triple
T21763344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max-E3-LIN-2 |
E537215
|
entity |
| Predicate | hasGapVersion |
P145850
|
FINISHED |
| Object | distinguish nearly satisfiable instances from highly unsatisfiable ones |
—
|
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: distinguish nearly satisfiable instances from highly unsatisfiable ones | Statement: [Max-E3-LIN-2, hasGapVersion, distinguish nearly satisfiable instances from highly unsatisfiable ones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGapVersion Context triple: [Max-E3-LIN-2, hasGapVersion, distinguish nearly satisfiable instances from highly unsatisfiable ones]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
C.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
D.
hasDifferentVersion
Indicates that one entity exists as a version that differs in some way from another entity.
-
E.
hasEarlierVersion
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a711dc8190a786c9849dc344e8 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.