Triple
T9606509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glottolog |
E231983
|
entity |
| Predicate | hasDataFormat |
P8462
|
FINISHED |
| Object | web interface |
—
|
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: web interface | Statement: [Glottolog, hasDataFormat, web interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataFormat Context triple: [Glottolog, hasDataFormat, web interface]
-
A.
hasFileFormat
chosen
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
B.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
C.
hasDataFields
Indicates that an entity possesses or is associated with specific data fields or attributes.
-
D.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
E.
hasDataFile
Indicates that an entity is associated with or linked to a specific data file that stores its related information.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a6006d48190adc03306533b9be6 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.