Triple
T32683579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APM line (Guangzhou Metro) |
E835654
|
entity |
| Predicate | hasOffPeakHeadway |
P114667
|
FINISHED |
| Object | approximately 3–6 minutes |
—
|
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: approximately 3–6 minutes | Statement: [APM line (Guangzhou Metro), hasOffPeakHeadway, approximately 3–6 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOffPeakHeadway Context triple: [APM line (Guangzhou Metro), hasOffPeakHeadway, approximately 3–6 minutes]
-
A.
offPeakServiceFrequency_minutes
chosen
Indicates the number of minutes between successive services during off-peak periods.
-
B.
hasPeakOffPeakDifferentiation
Indicates that there is a distinction between peak and off-peak periods in how something is applied, priced, or operated.
-
C.
hasOffPeakUsage
Indicates that an entity exhibits or is associated with usage occurring during designated off-peak times rather than standard peak periods.
-
D.
hasPeakHourFrequency
Indicates how often a service or event occurs during designated peak hours.
-
E.
hasPeakHourService
Indicates that a service operates or is available during designated peak or high-demand hours.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:09 a.m.