Triple
T17840960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book VI of A System of Logic |
E445522
|
entity |
| Predicate | appliesConceptsFrom |
P82547
|
FINISHED |
| Object | inductive logic |
—
|
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: inductive logic | Statement: [Book VI of A System of Logic, appliesConceptsFrom, inductive logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesConceptsFrom Context triple: [Book VI of A System of Logic, appliesConceptsFrom, inductive logic]
-
A.
exportsConcept
chosen
Indicates that one entity sends or supplies a concept, idea, or abstract knowledge resource from itself to another entity or context.
-
B.
updatesConceptsOf
Indicates that one entity modifies, revises, or refreshes the concepts associated with another entity.
-
C.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
usesConceptIdentifier
Indicates that one entity refers to or operates with a specific concept by means of its unique identifier.
-
E.
replacesConcept
Indicates that one concept takes the place of, or supersedes, another concept in a given context or system.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d2b2ea08190926ec0cf01285833 |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.