Triple
T7896712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C# lexical structure |
E183357
|
entity |
| Predicate | includesRuleType |
P2846
|
FINISHED |
| Object | tokenization rules |
—
|
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: tokenization rules | Statement: [C# lexical structure, includesRuleType, tokenization rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRuleType Context triple: [C# lexical structure, includesRuleType, tokenization rules]
-
A.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
B.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
typeOfRule
Indicates that one rule is classified as a specific kind or category of another, more general rule.
-
D.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
E.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a187a0081909a0c0822c6dab1da |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.