Triple
T32767840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearl River cruise piers in Guangzhou |
E837948
|
entity |
| Predicate | typicalOperatingTimeIncludes |
—
|
GENERATED |
| Object | evening |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOperatingTimeIncludes Context triple: [Pearl River cruise piers in Guangzhou, typicalOperatingTimeIncludes, evening]
-
A.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
B.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
C.
typicalDurationMinutes
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
-
D.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
E.
typicalSetupTime
Indicates the usual amount of time required to set something up or make it ready for use.
- F. None of above. chosen
Provenance (1 batch)
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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:13 a.m.