Triple
T23441671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meteora monastic community |
E565417
|
entity |
| Predicate | formerAccessMethods |
P120218
|
FINISHED |
| Object | ladders |
—
|
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: ladders | Statement: [Meteora monastic community, formerAccessMethods, ladders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAccessMethods Context triple: [Meteora monastic community, formerAccessMethods, ladders]
-
A.
formerAccess
chosen
Indicates that an entity previously had access to another entity or resource but no longer does.
-
B.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
C.
accessionMethod
Indicates the process or means by which something is acquired, obtained, or added to a collection or system.
-
D.
usesAccessMethod
Indicates that one entity employs or relies on a particular access method to reach, interact with, or retrieve another entity or resource.
-
E.
laterAccessedBy
Indicates that an entity is subsequently accessed or used by another entity at a later point in time.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a644f6948190af07b3c4c32fc7ae |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:51 p.m.