Triple
T25635855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsboro |
E642695
|
entity |
| Predicate | trialAlsoKnownAs |
P52192
|
FINISHED |
| Object | Hillsboro trial |
—
|
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: Hillsboro trial | Statement: [Hillsboro, trialAlsoKnownAs, Hillsboro trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialAlsoKnownAs Context triple: [Hillsboro, trialAlsoKnownAs, Hillsboro trial]
-
A.
trialName
chosen
Indicates the designated name or title assigned to a specific trial.
-
B.
trial
Indicates that an entity is the subject of a legal or formal judicial proceeding to determine guilt, liability, or resolution of a dispute.
-
C.
trialHeld
Indicates that a formal legal proceeding or court trial has taken place regarding a particular case or dispute.
-
D.
trialInstance
Indicates that one entity is a specific occurrence or execution of a broader trial, experiment, or test.
-
E.
trialHeldIn
Indicates that a legal trial took place or was conducted within a specified location or jurisdiction.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 5:22 p.m.