Triple
T1399930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami City Commission |
E30754
|
entity |
| Predicate | documentProduces |
P18123
|
FINISHED |
| Object | ordinances of the City of Miami |
—
|
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: ordinances of the City of Miami | Statement: [Miami City Commission, documentProduces, ordinances of the City of Miami]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentProduces Context triple: [Miami City Commission, documentProduces, ordinances of the City of Miami]
-
A.
documentTypeProduced
chosen
Indicates that one entity produces, generates, or creates a document of a specified type.
-
B.
producesFor
Indicates that one entity creates, manufactures, or generates something specifically intended for another entity’s use, benefit, or distribution.
-
C.
produces
Indicates that one entity creates, generates, or yields another entity as a result or output.
-
D.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
E.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39c4c148190997150996ca26a99 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.