Triple
T36707087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traité de chimie organique |
E906387
|
entity |
| Predicate | hasTheoreticalComponent |
P84902
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Traité de chimie organique, hasTheoreticalComponent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTheoreticalComponent Context triple: [Traité de chimie organique, hasTheoreticalComponent, yes]
-
A.
hasTheoreticalStatus
Indicates that something possesses a particular theoretical standing, classification, or role within a conceptual or theoretical framework.
-
B.
hasTheoreticalTreatment
chosen
Indicates that a subject is associated with, or described by, a theoretical explanation, model, or framework addressing it.
-
C.
hasTheory
Indicates that an entity possesses, is associated with, or is characterized by a particular theory.
-
D.
hasCoreTheory
Indicates that an entity is associated with, based on, or governed by a central underlying theory that defines its fundamental principles or framework.
-
E.
hasResearchComponent
Indicates that an entity includes, involves, or is associated with a research-related component or activity.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:12 p.m.