Triple
T5185454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idols of the Tribe |
E117019
|
entity |
| Predicate | isSourceOfErrorFor |
P32799
|
FINISHED |
| Object | scientific observation |
—
|
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: scientific observation | Statement: [Idols of the Tribe, isSourceOfErrorFor, scientific observation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSourceOfErrorFor Context triple: [Idols of the Tribe, isSourceOfErrorFor, scientific observation]
-
A.
isMajorSourceOf
chosen
Indicates that one entity serves as a primary or dominant origin, cause, or provider of another entity or effect.
-
B.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
C.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
-
D.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
E.
hasMainSource
Indicates that one entity serves as the primary or principal source or origin for 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c269148190badbaf9832a194c0 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.