Triple
T3539153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seri language |
E74839
|
entity |
| Predicate | hasNominalFeature |
P7162
|
FINISHED |
| Object | complex number system |
—
|
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: complex number system | Statement: [Seri language, hasNominalFeature, complex number system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNominalFeature Context triple: [Seri language, hasNominalFeature, complex number system]
-
A.
hasPostNominal
Indicates that an entity is associated with a post-nominal title, abbreviation, or letters that follow a name to denote qualifications, honors, or status.
-
B.
hasDistinctFeature
Indicates that an entity possesses a specific characteristic or attribute that differentiates it from others.
-
C.
hasLinguisticFeature
chosen
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
D.
nominalGamma
Indicates that something functions as a nominal element (e.g., noun-like role) within a grammatical or logical structure.
-
E.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcca5e008190abcfe40c8902a95f |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.