Triple
T24413994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grolier Codex |
E615530
|
entity |
| Predicate | scientificAnalysisResult |
P62814
|
FINISHED |
| Object | paper dated to 13th century |
—
|
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: paper dated to 13th century | Statement: [Grolier Codex, scientificAnalysisResult, paper dated to 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scientificAnalysisResult Context triple: [Grolier Codex, scientificAnalysisResult, paper dated to 13th century]
-
A.
analysisType
Indicates the specific kind or category of analysis being applied or performed in relation to an entity or dataset.
-
B.
hasAnalysis
chosen
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
C.
laboratoryAnalysis
Indicates that a sample or material is being examined, tested, or measured using scientific procedures in a laboratory setting.
-
D.
analyzes
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
-
E.
helpsAnalyze
Indicates that one entity assists another in examining, interpreting, or understanding something in a more detailed or effective way.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29583c2688190af3bc5d02eb9a3d9 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:12 a.m.