Triple
T26775754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Conference of Bar Examiners |
E670114
|
entity |
| Predicate | hasTestComponent |
P113722
|
FINISHED |
| Object | MBE |
—
|
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: MBE | Statement: [National Conference of Bar Examiners, hasTestComponent, MBE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTestComponent Context triple: [National Conference of Bar Examiners, hasTestComponent, MBE]
-
A.
hasComponentTest
chosen
Indicates that an entity includes or is associated with a specific test as one of its components.
-
B.
hasTestCapability
Indicates that an entity possesses the ability or functionality to perform a specified test or set of tests.
-
C.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
D.
hasFoundingComponent
Indicates that an entity includes another entity as a key element or constituent part involved in its founding or establishment.
-
E.
hasServerComponent
Indicates that an entity includes, depends on, or is associated with a particular server-side component.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 4:04 a.m.