Triple
T1357016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Family Court |
E29011
|
entity |
| Predicate | cannotGrant |
P27970
|
FINISHED |
| Object | divorces |
—
|
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: divorces | Statement: [New York Family Court, cannotGrant, divorces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotGrant Context triple: [New York Family Court, cannotGrant, divorces]
-
A.
cannot
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
B.
cannotReview
Indicates that an entity is not permitted or able to perform a review of another entity or item.
-
C.
cannotVeto
Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
-
D.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
E.
cannotIntroduce
Indicates that one entity is not permitted or able to introduce another entity (such as a person, concept, or item) into a given context or to a third party.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c28db5048190a279ee9882caaeaf |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c20fd1fc8190977a768b1ed2d23b |
completed | March 1, 2026, 10:47 p.m. |
Created at: March 1, 2026, 7:56 p.m.