Triple
T7868577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Hills, Los Angeles |
E182678
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Arleta |
E569858
|
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: Arleta | Statement: [Mission Hills, Los Angeles, adjacentTo, Arleta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arleta Context triple: [Mission Hills, Los Angeles, adjacentTo, Arleta]
-
A.
Arleta
chosen
Arleta is a residential neighborhood in the San Fernando Valley region of Los Angeles, California.
-
B.
Aleta
Aleta is a central character in the Prince Valiant saga, known as the intelligent and noble Queen of the Misty Isles and the beloved wife of the hero Prince Valiant.
-
C.
Arletta
Arletta, better known as Herleva of Falaise, was the mother of William the Conqueror and a notable figure in 11th-century Norman history.
-
D.
Anela
Anela is a small town and comune in the historical Logudoro region of northern Sardinia, Italy.
-
E.
Jolanda
Jolanda is a feminine given name, commonly considered a variant of Yolanda, used in various European countries.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3847c7fc819098e32b6548943da7 |
completed | March 31, 2026, 2:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5b60b3b08190832837bacb8ce965 |
completed | March 31, 2026, 5:28 a.m. |
Created at: March 30, 2026, 4:55 p.m.