Triple
T37637220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mfengu |
E936519
|
entity |
| Predicate | hasHistoricalLabel |
P111684
|
FINISHED |
| Object | Fingo people |
—
|
NE NERFINISHED |
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: Fingo people | Statement: [Mfengu, hasHistoricalLabel, Fingo people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalLabel Context triple: [Mfengu, hasHistoricalLabel, Fingo people]
-
A.
hasLabelHistory
chosen
Indicates that an entity is associated with a record of its past labels, including changes over time.
-
B.
hasHistoricalCategory
Indicates that something is associated with a particular historical classification, period, or type based on its past context or significance.
-
C.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
-
D.
hasHistoricMarker
Indicates that something is associated with or identified by an official historic marker or plaque recognizing its historical significance.
-
E.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:18 p.m.