Triple
T35482107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alayne Stone |
E1025495
|
entity |
| Predicate | claimedRegionOfOrigin |
P83441
|
FINISHED |
| Object | the Fingers |
—
|
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: the Fingers | Statement: [Alayne Stone, claimedRegionOfOrigin, the Fingers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedRegionOfOrigin Context triple: [Alayne Stone, claimedRegionOfOrigin, the Fingers]
-
A.
originalTerritory
chosen
Indicates that a specified area or region is the initial or historically established domain associated with an entity before any changes, transfers, or expansions.
-
B.
reportedRegion
Indicates that a specified region is the one referenced or identified in a report or reporting context.
-
C.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
-
D.
recognizedTerritory
Indicates that one entity formally acknowledges another entity’s claim of authority or ownership over a specific geographic area.
-
E.
calendarRegionOfOrigin
Indicates the geographic or cultural region from which a particular calendar system originates.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:04 p.m.