Triple
T29786411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thello |
E756276
|
entity |
| Predicate | operatesServiceBetween |
P194499
|
FINISHED |
| Object | France and Italy |
—
|
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: France and Italy | Statement: [Thello, operatesServiceBetween, France and Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesServiceBetween Context triple: [Thello, operatesServiceBetween, France and Italy]
-
A.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
-
B.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
-
C.
operatesBetween
Indicates a relationship where an action, process, or influence functions or takes effect in the space, interval, or context separating two entities.
-
D.
serviceBetween
chosen
Indicates that a service (such as transport, communication, or support) operates or is provided connecting two specified entities or locations.
-
E.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: April 29, 2026, 5:09 p.m.