Triple
T23458262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Library |
E567993
|
entity |
| Predicate | organizesCollectionBy |
P5709
|
FINISHED |
| Object | jurisdiction |
—
|
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: jurisdiction | Statement: [Law Library, organizesCollectionBy, jurisdiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizesCollectionBy Context triple: [Law Library, organizesCollectionBy, jurisdiction]
-
A.
organizesInto
chosen
Indicates that one entity arranges, structures, or groups another entity into a particular order, system, or set of categories.
-
B.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
-
C.
organizesLogicBy
Indicates a relationship where one entity structures, arranges, or systematizes another entity according to a particular logical framework or set of reasoning principles.
-
D.
organizedFrom
Indicates that something has been arranged, structured, or formed starting from a specified source or initial set of elements.
-
E.
fullyOrganizedBy
Indicates that an event, activity, or process is completely planned, coordinated, and managed by a specified organizing 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a69904588190b44c84021e94ae63 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.