Triple
T14084713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Peckham |
E338960
|
entity |
| Predicate | lieTo |
P24809
|
FINISHED |
| Object | south of Maidstone |
—
|
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: south of Maidstone | Statement: [East Peckham, lieTo, south of Maidstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lieTo Context triple: [East Peckham, lieTo, south of Maidstone]
-
A.
liesToThe
Indicates that one entity intentionally provides false or misleading information to another entity.
-
B.
liesBelow
chosen
Indicates that one entity is positioned at a lower vertical level than another entity.
-
C.
liesBeyond
Indicates that one entity is located at a greater distance or outside the boundary of another reference point, region, or limit.
-
D.
hasLie
Indicates that an entity is associated with or responsible for a specific lie or false statement.
-
E.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ede40048190b465e909565730c1 |
completed | April 14, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.