Triple
T1970740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Plaza |
E42792
|
entity |
| Predicate | hasTransferType |
P27343
|
FINISHED |
| Object | free transfer within complex |
—
|
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: free transfer within complex | Statement: [Queens Plaza, hasTransferType, free transfer within complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransferType Context triple: [Queens Plaza, hasTransferType, free transfer within complex]
-
A.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
B.
hasInterchangeType
Indicates that one entity is associated with a specific type or category of interchange (e.g., mode, format, or method of exchange) in relation to another entity.
-
C.
transferType
chosen
Indicates the specific method or category of how something is transferred from one entity to another.
-
D.
hasPaidTransfer
Indicates that a transfer of something (such as money, ownership, or rights) has been completed through a payment.
-
E.
hasTypeOfRecipient
Indicates that an entity is associated with a specific category or kind of recipient it is intended for or directed to.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3d2836c8190a35cb6d8e2dd4bdf |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.