Triple
T35029822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gmane |
E1010446
|
entity |
| Predicate | backupHostedAt |
P82607
|
FINISHED |
| Object | Internet Archive |
—
|
NE NERFINISHED |
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: Internet Archive | Statement: [Gmane, backupHostedAt, Internet Archive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupHostedAt Context triple: [Gmane, backupHostedAt, Internet Archive]
-
A.
backupFeatureIn
Indicates that one feature serves as a backup or fallback for another feature within a given context or system.
-
B.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
C.
hostingLocation
chosen
Indicates the place or venue where an event, activity, or entity is being hosted or takes place.
-
D.
servesAsBackupFor
Indicates that one entity functions as a substitute or fallback that can take over the role or responsibilities of another entity if needed.
-
E.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.