Triple
T10032271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If-None-Match |
E204878
|
entity |
| Predicate | conditionBasis |
P22542
|
FINISHED |
| Object | entity tag comparison |
—
|
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: entity tag comparison | Statement: [If-None-Match, conditionBasis, entity tag comparison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionBasis Context triple: [If-None-Match, conditionBasis, entity tag comparison]
-
A.
decisionBasis
Indicates the underlying reason, criterion, or rationale on which a decision is made.
-
B.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
C.
standingBasis
Indicates that one entity serves as the foundational reason, justification, or basis for another entity’s standing, status, or position in a given context.
-
D.
assessmentBasis
Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
-
E.
conditions
chosen
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce461d6481908cc8f968856e0337 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.