Triple
T15339848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comecrudo language |
E366759
|
entity |
| Predicate | dataCollectionCentury |
P26348
|
FINISHED |
| Object | 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: 19th century | Statement: [Comecrudo language, dataCollectionCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectionCentury Context triple: [Comecrudo language, dataCollectionCentury, 19th century]
-
A.
collectionEndCentury
chosen
Indicates the century in which a collection or collecting activity came to an end.
-
B.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
C.
discoveredInCentury
Indicates that an entity was discovered during a specific century.
-
D.
integrationCentury
Indicates the century during which an integration or unification process took place.
-
E.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e12eb7c8190944a260aa1aa9156 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.