Triple
T10251774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philosophy, Politics and Economics |
E240360
|
entity |
| Predicate | fieldCombines |
P70673
|
FINISHED |
| Object | philosophy |
—
|
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: philosophy | Statement: [Philosophy, Politics and Economics, fieldCombines, philosophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldCombines Context triple: [Philosophy, Politics and Economics, fieldCombines, philosophy]
-
A.
fieldComposition
Indicates how the components or elements within a field are organized, combined, or structured in relation to one another.
-
B.
combinedIn
chosen
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
symbolCombines
Indicates that multiple symbols are merged or joined together to form a single composite symbol or representation.
-
D.
combinationType
Indicates how multiple elements are combined or related to each other within a composite structure or operation.
-
E.
fieldIntersection
Indicates that two or more fields or domains share a common overlapping area or set of elements.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:29 a.m.