Triple
T25371900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFA |
E632951
|
entity |
| Predicate | formalLanguageClass |
P10465
|
FINISHED |
| Object | regular language |
—
|
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: regular language | Statement: [NFA, formalLanguageClass, regular language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalLanguageClass Context triple: [NFA, formalLanguageClass, regular language]
-
A.
inLanguageTheory
Indicates that something is analyzed, described, or formulated within a particular linguistic or formal language theory.
-
B.
linguisticClassification
chosen
Indicates the relationship by which an entity is categorized according to its language or linguistic type.
-
C.
公式言語
Indicates that something is expressed or represented using a formal language, typically defined by precise syntax and semantics.
-
D.
linguisticClassificationBasis
Indicates the criterion or principle used as the basis for classifying something within a linguistic system or framework.
-
E.
formalismFeature
Indicates that something is a characteristic, component, or property that belongs to or defines a particular formal system or formalism.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 1:38 p.m.