Triple
T24798092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bantu zone C |
E620443
|
entity |
| Predicate | hasTypicalCodePattern |
P157042
|
FINISHED |
| Object | C10–C90 |
—
|
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: C10–C90 | Statement: [Bantu zone C, hasTypicalCodePattern, C10–C90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalCodePattern Context triple: [Bantu zone C, hasTypicalCodePattern, C10–C90]
-
A.
hasTypicalSequence
Indicates that there is a usual or commonly occurring order or progression in which the related entities or events take place.
-
B.
hasStandardCode
Indicates that an entity is associated with a recognized standard code that formally identifies or classifies it.
-
C.
tailCodePattern
chosen
Indicates that an entity’s tail code follows or matches a specified pattern or format.
-
D.
hasTypeCode
Indicates that an entity is associated with a specific type classification represented by a code.
-
E.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 4:48 a.m.