Triple
T18015723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSGIRestrictProcess |
E430993
|
entity |
| Predicate | canBeDeclaredMultipleTimes |
P130120
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WSGIRestrictProcess, canBeDeclaredMultipleTimes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDeclaredMultipleTimes Context triple: [WSGIRestrictProcess, canBeDeclaredMultipleTimes, true]
-
A.
canBeMultiple
Indicates that the related item, value, or association is allowed to occur more than once rather than being restricted to a single instance.
-
B.
canBeAwardedMultipleTimes
Indicates that the associated award, honor, or recognition may be granted to the same recipient on more than one occasion.
-
C.
hasBeenDeclaredFor
Indicates that an entity has been officially announced, designated, or proclaimed for a particular purpose, status, or context.
-
D.
cannotBeAwardedMultipleTimes
Indicates that the same award or recognition cannot be granted to the same entity more than once.
-
E.
hasMultipleCreations
Indicates that an entity is associated with more than one distinct creation or produced work.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b523f588819097389e067dda7f23 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.