Triple
T26465113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culle |
E665739
|
entity |
| Predicate | phonologyDescription |
P94599
|
FINISHED |
| Object | poorly attested |
—
|
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: poorly attested | Statement: [Culle, phonologyDescription, poorly attested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phonologyDescription Context triple: [Culle, phonologyDescription, poorly attested]
-
A.
hasPhonologicalDescription
Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
-
B.
hasPhonologicalDescriptionStatus
chosen
Indicates that there exists a specified status or condition associated with the phonological description of an entity.
-
C.
hasPhonologicalParameters
Indicates that an entity is associated with specific phonological features or parameters that characterize its sound structure.
-
D.
primaryPhonologicalSystem
Indicates that one phonological system is the main or dominant sound system associated with a given language, dialect, or linguistic entity.
-
E.
hasOwnPhonology
Indicates that an entity possesses its own distinct phonological system or set of sound patterns, separate from those of other entities.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61298a2a48190b6677081992adcb2 |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:15 a.m.