Triple
T7884746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ekistics |
E183073
|
entity |
| Predicate | isInterdisciplinaryWith |
P592
|
FINISHED |
| Object | architecture |
—
|
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: architecture | Statement: [ekistics, isInterdisciplinaryWith, architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInterdisciplinaryWith Context triple: [ekistics, isInterdisciplinaryWith, architecture]
-
A.
isMultidisciplinary
Indicates that something involves or integrates multiple distinct academic or professional disciplines in its approach or composition.
-
B.
hasSubdiscipline
Indicates that one discipline includes another, more specialized field of study as a subordinate branch.
-
C.
studiedAlongWith
Indicates that two or more entities engaged in studying the same subject or course together during the same time period.
-
D.
hasInfluenceOnDiscipline
Indicates that one entity exerts an effect, shaping force, or contributing impact on the development, direction, or state of a particular discipline.
-
E.
associatedWithDiscipline
chosen
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39d62a148190bed4e0d199aa427b |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:59 p.m.