Triple
T4193549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | law of three stages |
E89089
|
entity |
| Predicate | appliedByComteTo |
P7760
|
FINISHED |
| Object | history of science |
—
|
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: history of science | Statement: [law of three stages, appliedByComteTo, history of science]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedByComteTo Context triple: [law of three stages, appliedByComteTo, history of science]
-
A.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
B.
appliedDoctrine
Indicates that a particular doctrine, principle, or rule has been put into practice or used in interpreting or deciding a specific case, situation, or context.
-
C.
appliesTheory
chosen
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
appliedBecauseOf
Indicates that one entity is applied, used, or enacted as a consequence or result of another specified cause or condition.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.