Triple
T876747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Lisbon |
E18933
|
entity |
| Predicate | hasSignificantActivityIn |
P19746
|
FINISHED |
| Object | scientific research |
—
|
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: scientific research | Statement: [University of Lisbon, hasSignificantActivityIn, scientific research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantActivityIn Context triple: [University of Lisbon, hasSignificantActivityIn, scientific research]
-
A.
hasActivityIn
chosen
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
C.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
D.
hasKeyActivity
Indicates that an entity is associated with or performs a primary or central activity.
-
E.
hasFanActivity
Indicates that an entity is associated with actions, behaviors, or engagement carried out by fans in relation to it.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acaf30a48190a10ed7fee464c444 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.