Triple
T35685806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily |
E1031143
|
entity |
| Predicate | assignedNumberBy |
P179557
|
FINISHED |
| Object | North Western Railway |
—
|
NE NERFINISHED |
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: North Western Railway | Statement: [Emily, assignedNumberBy, North Western Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedNumberBy Context triple: [Emily, assignedNumberBy, North Western Railway]
-
A.
assignedAs
Indicates that one entity is designated or appointed to perform a specific role, task, or function in relation to another entity.
-
B.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
C.
agentNumber
chosen
Indicates that a specific agent is associated with or responsible for a particular numerical identifier or count.
-
D.
assignedByCustom
Indicates that something has been assigned or allocated to an entity through a user-defined or non-standard assignment process.
-
E.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.