Triple
T38500784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanjong Beach |
E919825
|
entity |
| Predicate | timeOfHighUsage |
P34607
|
FINISHED |
| Object | weekends |
—
|
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: weekends | Statement: [Tanjong Beach, timeOfHighUsage, weekends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfHighUsage Context triple: [Tanjong Beach, timeOfHighUsage, weekends]
-
A.
usagePeak
chosen
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
B.
hasTimeOfHighActivity
Indicates that an entity experiences its peak or most intense level of activity during a specified time period.
-
C.
timeOfPeakSize
Indicates the specific time at which something reaches its maximum size or extent.
-
D.
maximumUsage
Indicates the highest allowable or observed amount, frequency, or extent to which something can be used within a defined context or period.
-
E.
recommendedUsageTime
Indicates the period of time for which something is advised or intended to be used.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:31 p.m.