Triple
T27615308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CodePlex |
E700424
|
entity |
| Predicate | readOnlyModeStartDate |
P72684
|
FINISHED |
| Object | 2017-10-01 |
—
|
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: 2017-10-01 | Statement: [CodePlex, readOnlyModeStartDate, 2017-10-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readOnlyModeStartDate Context triple: [CodePlex, readOnlyModeStartDate, 2017-10-01]
-
A.
effectivePeriodStart
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
B.
embargoStartDate
chosen
Indicates the date on which an embargo or restriction on access, release, or distribution begins to take effect.
-
C.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
-
D.
supportsDateRestrictions
Indicates that an entity can enforce or handle constraints based on specific dates or date ranges.
-
E.
previewStartDate
Indicates the date and time when a preview period for something begins.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f630d7de8c8190be167b89f6e54823 |
completed | May 2, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:12 p.m.