Triple
T7588088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westchester County Charter |
E179665
|
entity |
| Predicate | hasDocumentForm |
P27217
|
FINISHED |
| Object | written charter |
—
|
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: written charter | Statement: [Westchester County Charter, hasDocumentForm, written charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentForm Context triple: [Westchester County Charter, hasDocumentForm, written charter]
-
A.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
documentForm
chosen
Indicates the specific format or structural type in which a document is presented or recorded.
-
C.
containsForm
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
D.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
E.
hasWorkForm
Indicates that an entity is associated with a particular form, format, or mode in which its work or activity is carried out or expressed.
- 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f99875908190b09584cf13ea1e08 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.