Triple
T8646636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAL Form 4 – Crew’s Effects Declaration |
E204992
|
entity |
| Predicate | isSubmittedTo |
P28
|
FINISHED |
| Object | port customs authorities |
—
|
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: port customs authorities | Statement: [FAL Form 4 – Crew’s Effects Declaration, isSubmittedTo, port customs authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubmittedTo Context triple: [FAL Form 4 – Crew’s Effects Declaration, isSubmittedTo, port customs authorities]
-
A.
submittedTo
chosen
Indicates that one entity has formally sent or presented something (such as a document, request, or work) to another entity for consideration, review, or processing.
-
B.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
C.
submissionBasis
Indicates the basis, criteria, or grounds on which something is submitted or filed (e.g., a document, application, or claim).
-
D.
submissionSystem
Indicates a relationship where something is provided or turned in through a designated system or platform for receiving submissions.
-
E.
submissionStatus
Indicates the current state or phase of a submitted item within a review or processing workflow.
- 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_69ca834e56848190abb0eeaec9dedd32 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc480eb7f88190a38d2150976cd47f |
completed | March 31, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69cc45619460819091e83ffdec99c865 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:28 p.m.