Triple
T2288544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ħal Saflieni Hypogeum |
E51449
|
entity |
| Predicate | visitorLimitPerDay |
P427
|
FINISHED |
| Object | strictly limited |
—
|
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: strictly limited | Statement: [Ħal Saflieni Hypogeum, visitorLimitPerDay, strictly limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorLimitPerDay Context triple: [Ħal Saflieni Hypogeum, visitorLimitPerDay, strictly limited]
-
A.
visitorFrequency
Indicates how often a visitor comes to or interacts with a particular entity or location.
-
B.
rideLimit
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
-
C.
visitorCount
chosen
Indicates the number of visitors associated with a particular entity, context, or time period.
-
D.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2497ce881909b05eb9cec67d9e7 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.