Triple
T35035322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holland Land Company |
E1010893
|
entity |
| Predicate | soldLandOn |
P182029
|
FINISHED |
| Object | credit |
—
|
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: credit | Statement: [Holland Land Company, soldLandOn, credit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soldLandOn Context triple: [Holland Land Company, soldLandOn, credit]
-
A.
soldLandFor
Indicates that one party transferred ownership of land to another party in exchange for payment or other agreed compensation.
-
B.
soldProperty
Indicates that one entity transferred ownership of a property to another entity in exchange for payment.
-
C.
soldPropertyFor
Indicates that one entity transferred ownership of a property to another entity in exchange for a specified amount of money or value.
-
D.
leasedLandFor
Indicates that one party has granted another party the right to use a piece of land for a specified period under a lease agreement.
-
E.
soldWorkTo
Indicates that one entity transferred ownership of a work (such as a product, artwork, or creation) to another entity in exchange for payment.
- F. None of above. chosen
Provenance (4 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.