Triple
T9748369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-6 |
E236373
|
entity |
| Predicate | IUSStages |
P90479
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [STS-6, IUSStages, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IUSStages Context triple: [STS-6, IUSStages, 2]
-
A.
juridicalSchoolStatus
Indicates the legal or institutional status assigned to a school within a given jurisdiction or educational system.
-
B.
schoolOfJurisprudence
Indicates that one entity is a legal philosophy, doctrine, or interpretive framework to which the other entity (such as a jurist, decision, or institution) adheres or belongs.
-
C.
stateOfLaw
Indicates that a specified legal condition, rule, or status is currently in force or applicable within a given jurisdiction or context.
-
D.
judicialStatus
Indicates the legal or court-related condition or standing of an entity within a judicial process (e.g., pending, decided, appealed).
-
E.
canonicalJurisdictionOf
Indicates that one entity holds official legal or ecclesiastical authority over another entity or domain as its recognized jurisdiction.
- 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f68f8b88190b44babf5ae17dfef |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:23 p.m.