Triple
T4443698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSP (Communicating Sequential Processes) |
E96229
|
entity |
| Predicate | hasSemanticModel |
P28757
|
FINISHED |
| Object | trace semantics |
—
|
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: trace semantics | Statement: [CSP (Communicating Sequential Processes), hasSemanticModel, trace semantics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSemanticModel Context triple: [CSP (Communicating Sequential Processes), hasSemanticModel, trace semantics]
-
A.
hasSemantics
chosen
Indicates that one entity carries or encodes the meaning, interpretation, or semantic content associated with another entity.
-
B.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
-
C.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
-
D.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
E.
hasSchemaLanguage
Indicates that an entity uses, conforms to, or is defined in a particular schema language.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355b052688190a0d8e5912f82151c |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.