Triple
T3929300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Numic |
E93355
|
entity |
| Predicate | hasReconstructionLevel |
P51742
|
FINISHED |
| Object | phonological |
—
|
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: phonological | Statement: [Proto-Numic, hasReconstructionLevel, phonological]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReconstructionLevel Context triple: [Proto-Numic, hasReconstructionLevel, phonological]
-
A.
hasReconstructionStandard
Indicates that something is associated with or governed by a specific standard or guideline for how it should be reconstructed.
-
B.
hasAnimatedReconstruction
Indicates that an entity is associated with an animated reconstruction depicting it or one of its states or events.
-
C.
hasReconstructionWork
Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
-
D.
haveReconstructionWork
Indicates that an entity is undergoing or is associated with reconstruction or restoration work.
-
E.
hasReconstructedSite
Indicates that an entity has a site or location that has been rebuilt or restored after damage, destruction, or alteration.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeda65b708190b24cd715915aec1d |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb5f859c819095b61f5ba8eace4f |
completed | March 9, 2026, 3:46 p.m. |
Created at: March 9, 2026, 3:23 p.m.