Triple
T11779384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Chichester Roman road |
E280101
|
entity |
| Predicate | partiallyFollowedBy |
P25442
|
FINISHED |
| Object | modern roads |
—
|
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: modern roads | Statement: [London–Chichester Roman road, partiallyFollowedBy, modern roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyFollowedBy Context triple: [London–Chichester Roman road, partiallyFollowedBy, modern roads]
-
A.
partiallySuccessor
Indicates that one entity follows another in a sequence or process, but only to a limited or incomplete extent rather than as a full or direct successor.
-
B.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
C.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
D.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
E.
partiallyCorrespondsTo
chosen
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.