Triple
T3392373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee notes to rule amendments |
E71448
|
entity |
| Predicate | isPublishedWith |
P49368
|
FINISHED |
| Object | text of amended rules |
—
|
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: text of amended rules | Statement: [Committee notes to rule amendments, isPublishedWith, text of amended rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublishedWith Context triple: [Committee notes to rule amendments, isPublishedWith, text of amended rules]
-
A.
isPublished
Indicates that an item has been formally made available to the public through some publishing process.
-
B.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
C.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
D.
hasPublishedOn
Indicates that an entity (such as an author or publisher) has released or made content publicly available on a particular platform, medium, or date.
-
E.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb851e57c8190983cadcedc58db50 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb2e426b88190b82d9830149b142e |
completed | March 8, 2026, 5:33 p.m. |
Created at: March 8, 2026, 3:14 p.m.