Triple
T15312543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Z |
E366072
|
entity |
| Predicate | searchesResultedIn |
P118066
|
FINISHED |
| Object | multiple expeditions |
—
|
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: multiple expeditions | Statement: [City of Z, searchesResultedIn, multiple expeditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchesResultedIn Context triple: [City of Z, searchesResultedIn, multiple expeditions]
-
A.
searchResultsPoweredBy
Indicates that the displayed search results are generated or enhanced using a specific search provider, engine, or technology.
-
B.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
C.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve another entity.
-
D.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
E.
searchesConductedBy
Indicates that one entity performs or carries out search actions on behalf of or involving another entity.
- F. None of above. chosen
Provenance (4 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd2d5a88190aead748920f93d47 |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:16 a.m.