Triple
T31413974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technology and Construction Court |
E801341
|
entity |
| Predicate | governingGuide |
P18444
|
FINISHED |
| Object | Technology and Construction Court Guide |
—
|
NE NERFINISHED |
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: Technology and Construction Court Guide | Statement: [Technology and Construction Court, governingGuide, Technology and Construction Court Guide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingGuide Context triple: [Technology and Construction Court, governingGuide, Technology and Construction Court Guide]
-
A.
governingSee
Indicates that a governing authority observes, oversees, or monitors another entity or situation.
-
B.
providesGuidanceTo
chosen
Indicates that one entity offers direction, advice, or instruction to another entity.
-
C.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
D.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
E.
governingTour
Indicates that one entity conducts or oversees an official tour or guided visit for another entity.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: April 30, 2026, 8:41 p.m.