Triple
T6512600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poitevin-Saintongeais |
E150170
|
entity |
| Predicate | hasIETFTag |
P26071
|
FINISHED |
| Object | pcd |
E600830
|
NE 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: pcd | Statement: [Poitevin-Saintongeais, hasIETFTag, pcd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: pcd Context triple: [Poitevin-Saintongeais, hasIETFTag, pcd]
-
A.
pcd
chosen
pcd is the ISO 639-3 language code for Poitevin-Saintongeais, a Romance language spoken in western France.
-
B.
PCD
PCD is a U.S. Army facility in Colorado that stored and oversaw the destruction of chemical weapons as part of the nation’s chemical demilitarization program.
-
C.
PCL
PCL (Printer Command Language) is a page description language developed by Hewlett-Packard that became a widely used standard for controlling laser and inkjet printers.
-
D.
pvcs
pvcs is a software version control and configuration management system used to track and manage changes to source code and related files.
-
E.
PCN
PCN is the National Rail station code for Paisley Canal railway station in Paisley, Scotland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f3c5eb88190a56723acd8096dd8 |
completed | March 27, 2026, 3:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6d50f7d048190ad13dcd3f80c2eb4 |
completed | March 27, 2026, 7:05 p.m. |
Created at: March 27, 2026, 1:44 p.m.