Triple
T36544895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caradhras |
E901112
|
entity |
| Predicate | standsBetween |
P1262
|
FINISHED |
| Object | Eriador and Rhovanion |
—
|
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: Eriador and Rhovanion | Statement: [Caradhras, standsBetween, Eriador and Rhovanion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standsBetween Context triple: [Caradhras, standsBetween, Eriador and Rhovanion]
-
A.
locatedBetween
chosen
Indicates that one entity is positioned spatially between two other reference entities.
-
B.
takesPlaceBetween
Indicates that an event or interaction occurs within the temporal or spatial interval defined by two reference points.
-
C.
formedBetween
Indicates a relationship in which a connection, bond, or structure has come into existence linking two or more entities.
-
D.
standsAmid
Indicates being positioned in the middle of or surrounded by other things or people.
-
E.
actsBetween
Indicates an action or interaction that occurs from one entity to another, positioning the action as taking place in the relational space between them.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:11 p.m.