Triple
T14125373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludmilla |
E340016
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Parap |
E60401
|
NE 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: Parap | Statement: [Ludmilla, locatedNear, Parap]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parap Context triple: [Ludmilla, locatedNear, Parap]
-
A.
Parap
chosen
Parap is an inner-city suburb of Darwin in Australia's Northern Territory, known for its popular weekend markets and tropical, laid-back atmosphere.
-
B.
Parag
Parag is a given name most notably associated with Parag Agrawal, the former CEO of Twitter.
-
C.
Parah
Parah is a tractate of the Mishnah that deals with the laws of the red heifer and the ritual purification from corpse impurity.
-
D.
Parl
Parl is the commonly used abbreviation for the Parliament of Singapore, the country's unicameral legislative body.
-
E.
Paran
Paran is a wilderness region in the Hebrew Bible traditionally located in the northern Sinai or southern Transjordan, associated with Israelite wanderings and prophetic activity.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6096976481909dc79066c5165a50 |
completed | April 14, 2026, 3:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdf0a7a7c8190860d8ce47b5f0732 |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 10:22 p.m.