Triple
T7296504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bunyip Information Systems |
E164534
|
entity |
| Predicate | searchScope |
P23048
|
FINISHED |
| Object | internet file archives |
—
|
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: internet file archives | Statement: [Bunyip Information Systems, searchScope, internet file archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchScope Context triple: [Bunyip Information Systems, searchScope, internet file archives]
-
A.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
B.
searchesVia
chosen
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
C.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
-
D.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
locationScope
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8e48d48190ada4d507f3b61bc4 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.