Triple
T4074007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit City Charter |
E86716
|
entity |
| Predicate | publicDocument |
P53347
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Detroit City Charter, publicDocument, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicDocument Context triple: [Detroit City Charter, publicDocument, true]
-
A.
standardDocument
Indicates that an entity is a formal, authoritative document that defines standard specifications, rules, or guidelines to be followed.
-
B.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
C.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
D.
usedDocument
Indicates that one entity has employed, referenced, or otherwise made use of a particular document in performing an action or fulfilling a purpose.
-
E.
documentTypePublished
Indicates that a specific type or category of document has been formally published or made publicly available.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc245d888190ae773f9c3077953b |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa5c52648190b001027f4dba75cb |
completed | March 9, 2026, 4:50 p.m. |
Created at: March 9, 2026, 3:39 p.m.