Triple
T28996596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last-Modified |
E736181
|
entity |
| Predicate | canBeOmittedWhen |
P75771
|
FINISHED |
| Object | resource is known to change frequently |
—
|
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: resource is known to change frequently | Statement: [Last-Modified, canBeOmittedWhen, resource is known to change frequently]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeOmittedWhen Context triple: [Last-Modified, canBeOmittedWhen, resource is known to change frequently]
-
A.
mayBeOmittedWhen
chosen
Indicates that one element is allowed to be left out or excluded under certain conditions defined by another element or context.
-
B.
isOmittedFrom
Indicates that an entity is intentionally excluded or left out from a specified set, group, context, or representation.
-
C.
canBeEmpty
Indicates that something is allowed or able to have no content, elements, or value.
-
D.
canBeStripped
Indicates that one entity is capable of having an outer layer, covering, or component removed from it.
-
E.
canBeSuppressed
Indicates that the occurrence, effect, or expression of one entity can be reduced, inhibited, or prevented by another.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 28, 2026, 9:31 a.m.