Triple
T24550143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portugal women's national football team |
E607336
|
entity |
| Predicate | governedFromCity |
P6175
|
FINISHED |
| Object | Lisbon |
—
|
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: Lisbon | Statement: [Portugal women's national football team, governedFromCity, Lisbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedFromCity Context triple: [Portugal women's national football team, governedFromCity, Lisbon]
-
A.
governedFrom
chosen
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
-
B.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
C.
governedCityStateType
Indicates that a city is governed under a particular type or form of state-level governance.
-
D.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
E.
governingCityState
Indicates that one city or state holds governing authority or administrative control over another specified region or entity.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8ccddec8190819e6366b3d6b6f0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.