Triple
T32878359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schramm model of communication |
E840986
|
entity |
| Predicate | hasDiagramForm |
P79893
|
FINISHED |
| Object | circular model |
—
|
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: circular model | Statement: [Schramm model of communication, hasDiagramForm, circular model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiagramForm Context triple: [Schramm model of communication, hasDiagramForm, circular model]
-
A.
diagramType
chosen
Indicates the specific kind or category of diagram associated with an entity or context.
-
B.
hasChart
Indicates that one entity is associated with, represented by, or documented through a chart belonging to or describing it.
-
C.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
D.
hasCharting
Indicates that one entity provides or supports charting or graphical data visualization capabilities for another entity.
-
E.
hasPlanningForm
Indicates that an entity is associated with or characterized by a particular planning-related form, document, or structural representation used for planning.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 1, 2026, 1:18 a.m.