Triple
T32542438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | locally decodable codes |
E831746
|
entity |
| Predicate | researchedSince |
P119289
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [locally decodable codes, researchedSince, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchedSince Context triple: [locally decodable codes, researchedSince, 1990s]
-
A.
researchedAt
Indicates that an entity conducted research or scholarly work at a specified institution or location.
-
B.
hasBeenStudiedSince
chosen
Indicates that an entity has been the subject of study or research starting from a specified point in time and continuing thereafter.
-
C.
hasBeenStudiedFor
Indicates that an entity has been the subject of research, examination, or analysis for a specified purpose, topic, or application.
-
D.
hasResearched
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
-
E.
coordinatesResearchOn
Indicates that one entity organizes and directs the planning, execution, and integration of research activities involving another entity.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57fc940819086d7ab256f2cad71 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.