Triple
T375660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Appeals of Puerto Rico |
E8366
|
entity |
| Predicate | hasTypeOfCases |
P4217
|
FINISHED |
| Object | civil appeals |
—
|
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: civil appeals | Statement: [Court of Appeals of Puerto Rico, hasTypeOfCases, civil appeals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfCases Context triple: [Court of Appeals of Puerto Rico, hasTypeOfCases, civil appeals]
-
A.
hasTypeOfCase
chosen
Indicates that an entity is associated with or classified under a particular type or category of case.
-
B.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
C.
hasNumberOfCasesApprox
Indicates that an entity is associated with an approximate (not exact) count of cases.
-
D.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
E.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec169a848190a577aa093c878839 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96216048190873ae533fa5b864d |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.