Triple
T2553594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | trivago |
E56681
|
entity |
| Predicate | aggregatesFrom |
P2191
|
FINISHED |
| Object | online travel agencies |
—
|
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: online travel agencies | Statement: [trivago, aggregatesFrom, online travel agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregatesFrom Context triple: [trivago, aggregatesFrom, online travel agencies]
-
A.
collectsFrom
chosen
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
B.
aggregateState
Indicates the overall or combined condition or status resulting from multiple underlying states or components.
-
C.
convenesFrom
Indicates that an event, meeting, or gathering is initiated or brought together starting from a specified source, time, or context.
-
D.
areSometimesGroupedWith
Indicates that two or more entities are occasionally but not consistently classified, treated, or considered together as part of the same group.
-
E.
formedByUnionOf
Indicates that something is created or defined as the union or combination of multiple other things.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.