Triple
T22556873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enter to Learn, Go Forth to Serve |
E557708
|
entity |
| Predicate | phaseOrder |
P148642
|
FINISHED |
| Object | learning precedes service |
—
|
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: learning precedes service | Statement: [Enter to Learn, Go Forth to Serve, phaseOrder, learning precedes service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseOrder Context triple: [Enter to Learn, Go Forth to Serve, phaseOrder, learning precedes service]
-
A.
phaseIndicatedBy
Indicates that a particular phase or stage is determined, signaled, or specified by a given indicator or reference.
-
B.
phaseCount
Indicates the number of distinct phases or stages associated with a given process, event, or entity.
-
C.
phase
Indicates that one entity is in a particular stage, step, or phase within a process, sequence, or lifecycle relative to another reference.
-
D.
phaseUsed
Indicates that a particular phase, stage, or step is utilized or applied in carrying out an action, process, or relationship.
-
E.
phaseType
Indicates the specific stage or phase category that an associated process, event, or lifecycle instance belongs to.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7a4a3c81908fc87f48b6dcbbf7 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:52 p.m.