Triple
T9031742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ao Naga |
E216387
|
entity |
| Predicate | conversionWave |
P85783
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Ao Naga, conversionWave, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionWave Context triple: [Ao Naga, conversionWave, late 19th century]
-
A.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
B.
conversionTarget
Indicates that one entity serves as the intended outcome, goal, or result that another entity is meant to be converted or transformed into.
-
C.
conversionUse
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
-
D.
conversionEvent
Indicates that a user or entity has completed a desired target action (such as a purchase, signup, or other goal) that counts as a successful conversion.
-
E.
conversionStatus
Indicates the current state or outcome of a process in which one entity is transformed, converted, or transitioned into another form or status.
- F. None of above. chosen
Provenance (4 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6a9f2c7481909b4a272183f20585 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.