Triple
T278337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurkha units |
E5297
|
entity |
| Predicate | beganServiceIn |
P2339
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Gurkha units, beganServiceIn, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganServiceIn Context triple: [Gurkha units, beganServiceIn, early 19th century]
-
A.
enteredService
chosen
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
-
E.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dee7830819087f153769a8496b9 |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b765f488190b2cbe4b45cd42821 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.