Triple
T35035336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holland Land Company |
E1010893
|
entity |
| Predicate | recordsHeldAt |
P41398
|
FINISHED |
| Object | various archives in the United States |
—
|
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: various archives in the United States | Statement: [Holland Land Company, recordsHeldAt, various archives in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsHeldAt Context triple: [Holland Land Company, recordsHeldAt, various archives in the United States]
-
A.
recordHeldFor
Indicates that one entity is being kept, stored, or maintained on behalf of or in relation to another entity.
-
B.
recordHeldIn
chosen
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
C.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
D.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
E.
recordHeldAs
Indicates that one entity is maintained or kept in a particular form, status, or location as a record of another entity.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:01 p.m.