Triple
T31444922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaysian expressway network |
E802162
|
entity |
| Predicate | hasUntolledSections |
P50895
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Malaysian expressway network, hasUntolledSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUntolledSections Context triple: [Malaysian expressway network, hasUntolledSections, yes]
-
A.
hasUnmarkedSections
Indicates that certain sections within an entity lack required labels, annotations, or markings.
-
B.
hasDisciplineSections
Indicates that an entity is associated with one or more sections that belong to a particular discipline or field.
-
C.
hasTollFreeSection
chosen
Indicates that a route, road, or transportation facility includes at least one segment where no toll is charged for use.
-
D.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
-
E.
hasElevatedSections
Indicates that one entity contains or features parts that are raised or elevated relative to its other sections.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 30, 2026, 9:08 p.m.