Triple
T2682261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law School Admission Test |
E57398
|
entity |
| Predicate | writingSampleRequired |
P42222
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Law School Admission Test, writingSampleRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSampleRequired Context triple: [Law School Admission Test, writingSampleRequired, yes]
-
A.
writingForm
Indicates the specific script, notation, or written representation used to express a piece of language or content.
-
B.
writingSectionStatus
Indicates the current state or progress of a specific writing section within a larger document or workflow.
-
C.
writingTasks
Indicates that an entity is responsible for or engaged in performing writing-related tasks for another entity or context.
-
D.
writtenExamRequiredBefore
Indicates that completing a written exam is a prerequisite that must occur before another specified action or event.
-
E.
publicationRequirement
Indicates that an entity must be publicly disclosed or published as a condition for validity, compliance, or progression in a process.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abda2f7bf88190a1e3103dd014d871 |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ab9d08190b72b6104c6dbc769 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abda2dc5788190b4b83cb9ed08266c |
completed | March 7, 2026, 7:56 a.m. |
Created at: March 6, 2026, 9:54 p.m.