Triple
T379463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Lawyers Division |
E8644
|
entity |
| Predicate | hasSubunitType |
P7150
|
FINISHED |
| Object | committees |
—
|
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: committees | Statement: [Young Lawyers Division, hasSubunitType, committees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubunitType Context triple: [Young Lawyers Division, hasSubunitType, committees]
-
A.
subunitType
chosen
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
B.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
C.
hasSubdiscipline
Indicates that one discipline includes another, more specialized field of study as a subordinate branch.
-
D.
hasSubPeriod
Indicates that a time period is composed of or contains another, more specific time period as a subordinate part.
-
E.
hasSubstyle
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2b07248190979229bad3a741c9 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.