Triple
T37370922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pig |
E927839
|
entity |
| Predicate | standardServiceEntry |
P171454
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [The Pig, standardServiceEntry, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardServiceEntry Context triple: [The Pig, standardServiceEntry, 1959]
-
A.
serviceEntryWith
Indicates that one entity is associated with or accompanied by a particular service entry in a joint or linked context.
-
B.
standardServiceRoundOf
chosen
Indicates that one entity is the standard or typical service round associated with another entity (such as a process, schedule, or service context).
-
C.
serviceEntryInROC
Indicates that a service entry is recorded or included in a Register of Companies (ROC) or similar official registry.
-
D.
serviceEntryContext
Indicates the contextual circumstances or environment in which a particular service entry is created, recorded, or applied.
-
E.
ValiantServiceEntry
Indicates the performance or record of notably brave or heroic service carried out by an entity.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 3, 2026, 4:16 p.m.