Triple
T31768155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samia |
E810863
|
entity |
| Predicate | hasTypologyFeature |
P29386
|
FINISHED |
| Object | noun class 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: noun class system | Statement: [Samia, hasTypologyFeature, noun class system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypologyFeature Context triple: [Samia, hasTypologyFeature, noun class system]
-
A.
isFeatureOf
chosen
Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
-
B.
hasTopologicalFeature
Indicates that an entity possesses a specific topological characteristic or feature, such as a property related to continuity, connectivity, or spatial structure.
-
C.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
D.
proposesTypologyOf
Indicates that one entity puts forward or formulates a systematic classification or typology concerning another entity.
-
E.
hasFolkloreType
Indicates that something is associated with, categorized under, or characterized by a particular type of folklore.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: April 30, 2026, 11:33 p.m.