Triple
T21863780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Order No. 3 |
E539831
|
entity |
| Predicate | orderNumberWithinDepartment |
P145963
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [General Order No. 3, orderNumberWithinDepartment, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderNumberWithinDepartment Context triple: [General Order No. 3, orderNumberWithinDepartment, 3]
-
A.
departmentNumber
Indicates the specific numeric code assigned to identify a particular department within an organization or system.
-
B.
orderNumber
Indicates the unique identifier assigned to a specific order within a transaction or ordering process.
-
C.
orderWithin
Indicates that one entity is positioned or ranked before or after another entity within a defined sequence or ordering.
-
D.
basedInDepartment
Indicates that an entity operates or has its primary affiliation within a specific department.
-
E.
offeredByDepartment
Indicates that something, such as a course or program, is provided or made available by a specific department.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63d927c8190bcfccc140357484c |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:56 p.m.