Triple
T37789230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSRS |
E942035
|
entity |
| Predicate | closedToNewEntrants |
P144331
|
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: [CSRS, closedToNewEntrants, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToNewEntrants Context triple: [CSRS, closedToNewEntrants, true]
-
A.
closedToNewApplications
chosen
Indicates that the subject is no longer accepting any new applications.
-
B.
closedOffFrom
Indicates that one entity is isolated, blocked, or prevented from accessing, interacting with, or being influenced by another entity.
-
C.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
D.
closedToNewClaims
Indicates that no additional claims can be initiated or submitted under the referenced item, case, or policy.
-
E.
closedToPublic
Indicates that access to the referenced entity is restricted so that the general public is not allowed to enter or use it.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:19 p.m.