Triple
T28189178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Language Server Index Format |
E716253
|
entity |
| Predicate | typicalProducer |
P202303
|
FINISHED |
| Object | language-specific indexer |
—
|
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: language-specific indexer | Statement: [Language Server Index Format, typicalProducer, language-specific indexer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProducer Context triple: [Language Server Index Format, typicalProducer, language-specific indexer]
-
A.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
B.
traditionalProducer
Indicates that an entity produces something using traditional, customary, or long-established methods or practices.
-
C.
primaryProducer
Indicates that an entity produces a good, service, or resource as the initial source in a supply, economic, or ecological chain.
-
D.
producerName
Indicates that the associated value is the name of the producer responsible for creating or manufacturing the referenced entity.
-
E.
producerOfWork
Indicates that one entity is the creator or originator responsible for producing a particular work.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
| PDg | Predicate description generation | batch_6a00708a01d08190a290fabcb435c358 |
completed | May 10, 2026, 11:48 a.m. |
Created at: April 27, 2026, 10:24 p.m.