Triple
T95853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pascal |
E1927
|
entity |
| Predicate | scopeRule |
P2846
|
FINISHED |
| Object | lexical scoping |
—
|
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: lexical scoping | Statement: [Pascal, scopeRule, lexical scoping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeRule Context triple: [Pascal, scopeRule, lexical scoping]
-
A.
notableRule
Indicates that a rule or regulation is particularly significant, prominent, or noteworthy within a given context.
-
B.
sharesRulesWith
Indicates that two entities follow, are governed by, or operate under the same set of rules or regulations.
-
C.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
D.
restriction
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
E.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a250cb400c8190b56343bbe19b48c7 |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ebd19c48190bab291fea0ecc0c2 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.